Hello,
we want to upgrade a PVE Cluster with several hosts (>10) to Version 6 from various versions of 5.x. All are using the enterprise repositories.
The Process, according to the docs, is this:
Phase 1: Firstly, upgrade ALL packages on all hosts to be at the latest patch level of PVE 5.4. Have apt list --upgradable completely empty. In general, requires node reboots. We think this can be stretched out over some days.
Phase 2: Using the transitional stretch/corosync3 repo, upgrade corosync from v2 to v3 everywhere (because of the inevitable quorum loss in the smaller partition at any time, do this fast). Does NOT require reboots.
Phase 3: Upgrade all hosts to Proxmox 6.x (now 6.2) / Debian Buster. Requires node reboots again, but can be stretched out over some days, we think.
We tested this on a productive 2 node cluster, and on a 3 node test ceph cluster with some Test VMs (hyper-converged). Worked well.
But on this larger cluster, we will have trouble getting EVERYTHING up to date EVERYWHERE before the corosync upgrade.
I upgraded a node (node 1) 2 days earlier, and at the time, it had everything up to date.
Today, i upgraded 2 more nodes (node 2 and 4). But now node 1 is already not completely up to date anymore. Possible upgrades:
pve-kernel (5.4-16 -> 5.4.17)
pve-manager (5.4-13 -> 5.4-15)
(proxmox-ve is 5.4-2 on all 3 nodes)
The 5to6-Manual at the wiki states explicitly to make sure NOTHING but corosync and its dependencies will be upgraded when moving up to corosync3. It even lists the exact packages expected.
So, no minor possible upgrade of pve-kernel, or pve-manager. Need to upgrade those first, again.
But is this really strictly necessary? Or is it just a warning to make sure you don't accidentally upgrade a node to v6.x before upgrading everything to corosync3, and to make sure you are at proxmox-ve 5.4-2 ?
If it really IS necessary, does that also mean i need to reboot (host 1) again before the corosync3 upgrade (in general? or maybe only in this instance, to get the new kernel running?)
Getting all node to exactly the same patch levels of every installed package prior to the corosync upgrade may be difficult, especially if this requires reboots. In general, we may need to migrate machines, make fresh backups, and coordinate with people at short notice before any single upgrade+reboot, and check everything after any upgrade.
we want to upgrade a PVE Cluster with several hosts (>10) to Version 6 from various versions of 5.x. All are using the enterprise repositories.
The Process, according to the docs, is this:
Phase 1: Firstly, upgrade ALL packages on all hosts to be at the latest patch level of PVE 5.4. Have apt list --upgradable completely empty. In general, requires node reboots. We think this can be stretched out over some days.
Phase 2: Using the transitional stretch/corosync3 repo, upgrade corosync from v2 to v3 everywhere (because of the inevitable quorum loss in the smaller partition at any time, do this fast). Does NOT require reboots.
Phase 3: Upgrade all hosts to Proxmox 6.x (now 6.2) / Debian Buster. Requires node reboots again, but can be stretched out over some days, we think.
We tested this on a productive 2 node cluster, and on a 3 node test ceph cluster with some Test VMs (hyper-converged). Worked well.
But on this larger cluster, we will have trouble getting EVERYTHING up to date EVERYWHERE before the corosync upgrade.
I upgraded a node (node 1) 2 days earlier, and at the time, it had everything up to date.
Today, i upgraded 2 more nodes (node 2 and 4). But now node 1 is already not completely up to date anymore. Possible upgrades:
pve-kernel (5.4-16 -> 5.4.17)
pve-manager (5.4-13 -> 5.4-15)
(proxmox-ve is 5.4-2 on all 3 nodes)
The 5to6-Manual at the wiki states explicitly to make sure NOTHING but corosync and its dependencies will be upgraded when moving up to corosync3. It even lists the exact packages expected.
So, no minor possible upgrade of pve-kernel, or pve-manager. Need to upgrade those first, again.
But is this really strictly necessary? Or is it just a warning to make sure you don't accidentally upgrade a node to v6.x before upgrading everything to corosync3, and to make sure you are at proxmox-ve 5.4-2 ?
If it really IS necessary, does that also mean i need to reboot (host 1) again before the corosync3 upgrade (in general? or maybe only in this instance, to get the new kernel running?)
Getting all node to exactly the same patch levels of every installed package prior to the corosync upgrade may be difficult, especially if this requires reboots. In general, we may need to migrate machines, make fresh backups, and coordinate with people at short notice before any single upgrade+reboot, and check everything after any upgrade.
