Skip to content
Snippets Groups Projects
Commit f1f5523c authored by Julien Leduc's avatar Julien Leduc
Browse files

Using /EOSOK file to check that eos instance has been launched successfully...

Using /EOSOK file to check that eos instance has been launched successfully and not kubectl logs as there is no log with systemd.
parent 07ba819c
No related branches found
No related tags found
No related merge requests found
......@@ -182,7 +182,7 @@ test -e /usr/lib64/libjemalloc.so.1 && export LD_PRELOAD=/usr/lib64/libjemalloc.
# configure preprod directory separately
/opt/run/bin/eos_configure_preprod.sh
echo "### ctaeos mgm ready ###"
touch /EOSOK
/bin/bash
......@@ -306,10 +306,10 @@ echo OK
echo -n "Waiting for EOS to be configured"
for ((i=0; i<300; i++)); do
echo -n "."
kubectl --namespace=${instance} logs ctaeos | grep -q "### ctaeos mgm ready ###" && break
[ "`kubectl --namespace=${instance} exec ctaeos -- bash -c "[ -f /EOSOK ] && echo -n Ready || echo -n Not ready"`" = "Ready" ] && break
sleep 1
done
kubectl --namespace=${instance} logs ctaeos | grep -q "### ctaeos mgm ready ###" || die "TIMED OUT"
[ "`kubectl --namespace=${instance} exec ctaeos -- bash -c "[ -f /EOSOK ] && echo -n Ready || echo -n Not ready"`" = "Ready" ] || die "TIMED OUT"
echo OK
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment