From db93af27b289ae409ff1c5661fdb83a0f8d5c5ce Mon Sep 17 00:00:00 2001 From: "goodolclint-claude[bot]" <323206664+goodolclint-claude[bot]@users.noreply.github.com> Date: Tue, 1 Sep 2026 06:18:48 +0000 Subject: [PATCH] ci: capture cluster task logs in the diagnostics "Cluster join aborted!" is PVE's generic wrapper; the reason lives only in the task log on the joining node. Run 172's log said "An error occurred on the cluster node: cluster not ready - no quorum?", which is what identified the race. Capture it so the evidence survives cleanup. Co-Authored-By: Claude Opus 5 (1M context) --- tests/infrastructure/scripts/diagnose-cluster.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/infrastructure/scripts/diagnose-cluster.sh b/tests/infrastructure/scripts/diagnose-cluster.sh index e7312a0..e5c01d1 100644 --- a/tests/infrastructure/scripts/diagnose-cluster.sh +++ b/tests/infrastructure/scripts/diagnose-cluster.sh @@ -66,6 +66,11 @@ journalctl -u corosync -n 60 --no-pager 2>&1 echo echo "--- journalctl -u pve-cluster (last 30) ---" journalctl -u pve-cluster -n 30 --no-pager 2>&1 +echo +echo "--- cluster task logs ---" +# "Cluster join aborted!" is generic; the reason is only in the task log. +find /var/log/pve/tasks -type f \( -name '*clusterjoin*' -o -name '*clustercreate*' \) \ + -exec echo "== {} ==" \; -exec cat {} \; 2>&1 | tail -80 REMOTE }