From 3d67d9f5ebf2fa14ee12adaea5a152212b2f31eb Mon Sep 17 00:00:00 2001 From: Rafael Santos Date: Mon, 9 Sep 2024 11:07:04 -0300 Subject: [PATCH] Use the parameter --wait to check if pods started There was this parameter --wait to check if the pods are running before proceed and we are implementing the use of it on this commit. Test plan: Run the pipeline. Change-Id: I5207d41b0c66d63269673f9f2762a351aa382353 Signed-off-by: Rafael Santos --- scripts/start-containers.sh | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/scripts/start-containers.sh b/scripts/start-containers.sh index 1df64fe..00f62e3 100755 --- a/scripts/start-containers.sh +++ b/scripts/start-containers.sh @@ -16,17 +16,9 @@ require_job_env BUILDER_POD_STARTUP_TIMEOUT set -x stx control stop stx config --upgrade -stx control start +### There is a timeout of 5 minutes on the --wait parameter +stx control start --wait -# wait for startup -notice "waiting for containers to startup ($BUILDER_POD_STARTUP_TIMEOUT seconds)" -let deadline="$(date '+%s')+$BUILDER_POD_STARTUP_TIMEOUT" -until check_all_pods_running ; do - if [[ "$(date '+%s')" -ge $deadline ]] ; then - die "pods didn't start up after $BUILDER_POD_STARTUP_TIMEOUT second(s)" - fi - sleep 10 -done stx control status # Add ssh access key to signing server