ci.ocp: Improve the service-up detection

waiting for the first response is not sufficient as OCP returns html page without error even when the route is not yet established describing the issue (why it doesn't reply with 500?). Waiting for the correct output should do better. Signed-off-by: Lukáš Doktor <[email protected]>
kata-containers · Feb 7, 2024 · 6669db0 · 6669db0
1 parent f15be37
commit 6669db0
Showing 1 changed file with 11 additions and 6 deletions.
diff --git a/.ci/openshift-ci/run_smoke_test.sh b/.ci/openshift-ci/run_smoke_test.sh
@@ -57,14 +57,19 @@ else
 fi
 
 info "Wait for the HTTP server to respond"
-rm -f hello_msg.txt
-waitForProcess 60 1 "curl '${host}:${port}${hello_file}' -s -o hello_msg.txt"
-
-grep "${hello_msg}" hello_msg.txt > /dev/null
-test_status=$?
-if [ $test_status -eq 0 ]; then
+if waitForProcess 60 1 "curl '${host}:${port}${hello_file}' 2>/dev/null | grep -q '$hello_msg'"; then
+	test_status=0
 	info "HTTP server is working"
 else
+	test_status=1
+	echo "::error:: HTTP server not working"
+	curl -vvv "${host}:${port}${hello_file}"
+	echo "::group::Describe kube-system namespace"
+	oc describe -n kube-system all
+	echo "::endgroup::"
+	echo "::group::Descibe current namespace"
+	oc describe all
+	echo "::endgroup::"
 	info "HTTP server is unreachable"
 fi