From ea37f5ac8ef2c79e2eaac3e3ed82b0296e87aa1f Mon Sep 17 00:00:00 2001 From: Pasquale Congiusti Date: Tue, 29 Oct 2024 18:43:14 +0100 Subject: [PATCH] chore(ci): increase timeout --- .github/workflows/nightly-install-olm.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/nightly-install-olm.yml b/.github/workflows/nightly-install-olm.yml index 96fbee3466..88cb6ba3cd 100644 --- a/.github/workflows/nightly-install-olm.yml +++ b/.github/workflows/nightly-install-olm.yml @@ -55,7 +55,7 @@ jobs: run: | kubectl create -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.28.0/crds.yaml kubectl create -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.28.0/olm.yaml - kubectl wait --for=jsonpath='{.status.phase}'=Succeeded csv packageserver -n olm --timeout=2m + kubectl wait --for=jsonpath='{.status.phase}'=Succeeded csv packageserver -n olm --timeout=5m # Building and pushing a bundle to a running container is required due to how # Operator-SDK works. Once it allows for local bundle testing, this part may be omitted