From d80a1e4327153d828786e284cc11310bbd1664c8 Mon Sep 17 00:00:00 2001 From: Yoni Bettan Date: Mon, 13 Jan 2025 09:22:56 +0200 Subject: [PATCH] Retrying applying CRs in the `e2e` jobs. (#1293) The webhook services are not always available right after the deployments are ready. This is causing a race condition between the services being ready to get requests and the CRs applied to the cluster. By retrying to apply the CRs we can give the services the time they need to become ready. Signed-off-by: Yoni Bettan --- ci/prow/e2e-hub-spoke-incluster-build | 2 +- ci/prow/e2e-incluster-build | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ci/prow/e2e-hub-spoke-incluster-build b/ci/prow/e2e-hub-spoke-incluster-build index ec1224ee2..a53b7ff66 100755 --- a/ci/prow/e2e-hub-spoke-incluster-build +++ b/ci/prow/e2e-hub-spoke-incluster-build @@ -51,7 +51,7 @@ else fi # Apply resources -oc apply -k ci/e2e-hub +timeout 1m bash -c 'until oc apply -k ci/e2e-hub; do sleep 3; done' # Wait for the build build to be created and completed timeout 1m bash -c 'until oc -n ${HUB_OPERATOR_NAMESPACE} get builds -o json | jq -er ".items[].metadata.name | select(.? | match(\"build\"))"; do sleep 1; done' diff --git a/ci/prow/e2e-incluster-build b/ci/prow/e2e-incluster-build index 995054cb3..192c4905d 100755 --- a/ci/prow/e2e-incluster-build +++ b/ci/prow/e2e-incluster-build @@ -41,7 +41,7 @@ oc debug "node/${NODE}" -- chroot host/ lsmod | grep dummy oc wait --for=condition=Available deployment/kmm-operator-controller deployment/kmm-operator-webhook -n openshift-kmm echo "Add resources" -oc apply -k ci/e2e +timeout 1m bash -c 'until oc apply -k ci/e2e; do sleep 3; done' # Wait for the build pod to be created. `kubectl wait` doesn't support such option, # see https://github.com/kubernetes/kubernetes/issues/83242.