mirror of
https://github.com/GoodOlClint/PSProxmoxVE.git
synced 2026-09-04 03:05:32 +00:00
goodolclint-claude[bot]
5e046e3d31
`apt-get upgrade` holds back any package whose upgrade needs new dependencies, so it neither pins nor updates — it produces whatever partial set the dependency graph allows that day. On these nodes it upgraded pve-cluster to 9.1.6 while leaving libpve-cluster-api-perl at 9.1.0. Those two ship the halves of the join: cfs_backup_database() in PVE/Cluster.pm (pve-cluster) and finish_join() in PVE/Cluster/Setup.pm (libpve-cluster-api-perl). Upstream removed `return $dbfile` from the former and stopped relying on it in the latter, both at 9.1.1 — 9.1.6's finish_join calls cfs_unlink_db_unsafe() instead. The 9.1.0 caller against the 9.1.6 callee unlinks an empty string, so the standalone config.db survives the join, pmxcfs restarts in local mode, and the node reports online=0 forever while corosync forms a healthy 2-node membership. That is the "2 nodes online" failure, and it is not reachable on any coherent install. The ISO is the pin, so drop the upgrade and install only what the harness needs. Upgrades belong in a separate currency lane that records the package set it tested. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>