From 8dde5f39b717430222a3974d43f056792017205b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Wed, 6 May 2026 09:29:13 +0200 Subject: [PATCH] tests: dump kata-deploy pod describe+logs on install timeout MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When kubectl wait times out the pod never reached Ready, so the existing log collection (which runs after wait succeeds) produces "-- No entries --" with zero useful information. Capture kubectl describe and kubectl logs (including previous container) immediately on timeout so the next CI run shows exactly why the pod is stuck (ImagePullBackOff, OOMKilled, probe failures, containerd restart hang, etc.). Signed-off-by: Fabiano Fidêncio Assisted-by: Cursor --- tests/gha-run-k8s-common.sh | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/tests/gha-run-k8s-common.sh b/tests/gha-run-k8s-common.sh index ed98ecd72e..9f8c42eb17 100644 --- a/tests/gha-run-k8s-common.sh +++ b/tests/gha-run-k8s-common.sh @@ -1065,7 +1065,16 @@ VERIFICATION_POD_EOF fi sleep 1 done - kubectl -n kube-system wait pod -l name=kata-deploy --for=condition=Ready --timeout="${KATA_DEPLOY_WAIT_TIMEOUT}s" + if ! kubectl -n kube-system wait pod -l name=kata-deploy --for=condition=Ready --timeout="${KATA_DEPLOY_WAIT_TIMEOUT}s"; then + echo "::group::kata-deploy pod describe (install timed out)" + kubectl -n kube-system describe pod -l name=kata-deploy || true + echo "::endgroup::" + echo "::group::kata-deploy logs (install timed out)" + kubectl -n kube-system logs -l name=kata-deploy --all-containers --previous 2>/dev/null || true + kubectl -n kube-system logs -l name=kata-deploy --all-containers 2>/dev/null || true + echo "::endgroup::" + return 1 + fi echo "::group::kata-deploy logs" kubectl_retry -n kube-system logs -l name=kata-deploy