gsadmin/PSProxmoxVE
1
0
Fork 0
mirror of https://github.com/GoodOlClint/PSProxmoxVE.git synced 2026-09-03 18:55:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: capture cluster task logs in the diagnostics

Browse Source 
"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) <noreply@anthropic.com>
This commit is contained in:
goodolclint-claude[bot]
2026-09-01 06:18:48 +00:00
committed by GitHub
parent 4294407d80
commit db93af27b2
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/infrastructure/scripts/diagnose-cluster.sh
+5
View File
@@ -66,6 +66,11 @@ journalctl -u corosync -n 60 --no-pager 2>&1
echo echo
echo "--- journalctl -u pve-cluster (last 30) ---" echo "--- journalctl -u pve-cluster (last 30) ---"
journalctl -u pve-cluster -n 30 --no-pager 2>&1 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 REMOTE
} }