From c03b1f6a45e86fda98e8b86c982a7f46c33c5cd6 Mon Sep 17 00:00:00 2001 From: Matthew Fuller Date: Wed, 26 May 2021 09:27:44 +0000 Subject: [PATCH] [FIX] Fix timeout error waiting for bmh ready There appears to be a race condition in the kubectl_wait_bmh.sh script. It waits for the bmh to reach provisioning state 'ready', but it may have already moved into 'provisioning' state between checks. Changed the script to wait for the final 'provisioned' state instead. Change-Id: I3d825e8d6b2b4d3f2a4b15fe4c2823fb03588405 --- manifests/function/phase-helpers/wait_bmh/kubectl_wait_bmh.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manifests/function/phase-helpers/wait_bmh/kubectl_wait_bmh.sh b/manifests/function/phase-helpers/wait_bmh/kubectl_wait_bmh.sh index 590e66678..6ee68b8c5 100644 --- a/manifests/function/phase-helpers/wait_bmh/kubectl_wait_bmh.sh +++ b/manifests/function/phase-helpers/wait_bmh/kubectl_wait_bmh.sh @@ -27,7 +27,7 @@ do if [ "$(kubectl --request-timeout 20s \ --context $KCTL_CONTEXT \ get bmh $worker \ - -o jsonpath='{.status.provisioning.state}')" == "ready" ] ; then + -o jsonpath='{.status.provisioning.state}')" == "provisioned" ] ; then echo "Get BMHs status" 1>&2 kubectl \