Maarten ca660585dc Correct reboot diagnosis: OC-specific, not dqlite/TPM corruption ... Volume testing with live Proxmox infrastructure proved that guest reboot does NOT break standalone IncusOS nodes. Tested: - 4 consecutive Proxmox stop/start cycles: all clean, data intact - Single-node guest reboot: recovered in ~50s, containers auto-started - Simultaneous 3-node guest reboot: all recovered, data integrity verified The "reboot breaks IncusOS" issue is OC-specific. Console errors showed: - Node 1: "failed to parse update frequency" (OC pushed bad crontab) - Node 2: stuck at "starting application" (waiting for peers in loops) - Node 3: "constraint violation" (OC re-registering existing server) Updated all 8 references across CLAUDE.md, operations-center-guide.md, and TESTING.md to reflect the corrected diagnosis. Also fixed one more bare return bug in do_list_labs (empty pool path). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-02-21 00:48:06 +01:00
..
clustering-guide.md	Add advanced migration testing, cluster lifecycle, and clustering guide	2026-02-20 18:46:55 +01:00
incus-version-compatibility.md	version and certificate refinement	2026-02-18 14:49:31 +01:00
iso-download-methods.md	Initial Commit	2026-02-18 14:04:05 +01:00
migration-guide.md	Add macOS support, multi-lab lifecycle, extended testing, and migration docs	2026-02-20 23:41:06 +01:00
operations-center-guide.md	Correct reboot diagnosis: OC-specific, not dqlite/TPM corruption	2026-02-21 00:48:06 +01:00
proxmox-deploy-progress.md	Implement end-to-end IncusOS Proxmox deployment via API	2026-02-19 15:26:58 +01:00
utm-support.md	Add macOS support, multi-lab lifecycle, extended testing, and migration docs	2026-02-20 23:41:06 +01:00