[SOLVED] Ceph Update Nautilus -> Octopus on pve6.1 in preparation to pve7 upgrade

[udo]

Hi,
we would update our pve-cluster to pve7 and like to reduce the reboots to one for each node.
Ceph is allready on 14.2.22.
The howto say: "We assume that all nodes are on the latest Proxmox VE 6.3 (or higher)", which isn't on most nodes in our cluster.

Is it still posible to upgrade ceph to Octopus first? We don't need the pve-gui for handling ceph. It's only necessary that the VMs, which run on ceph, are running without disruption.
An normal dist-upgrade (6.4) isn't possible without downtime for the VMs due an openvswitch-upgrade (last openvswitch-upgrades produce network interruption for all VMs).

After upgrade to Octopus we will upgrade each node to the latest pve6 plus dist-upgrade to pve7.


Udo

 

[t.lamprecht]

The howto say: "We assume that all nodes are on the latest Proxmox VE 6.3 (or higher)", which isn't on most nodes in our cluster.

PVE 6.3 can be fine for Nautilus -> Octopus, but for 6 -> 7 you need latest 6.4, so I'd recommend updating to that now already, a full reboot isn't a hard requirement if you plan to go to 7.x directly afterwards.

Is it still posible to upgrade ceph to Octopus first? We don't need the pve-gui for handling ceph. It's only necessary that the VMs, which run on ceph, are running without disruption.

Yes, you can (and even must) upgrade to octopus before starting out the upgrade to Proxmox VE 7.x.

An normal dist-upgrade (6.4) isn't possible without downtime for the VMs due an openvswitch-upgrade (last openvswitch-upgrades produce network interruption for all VMs).

Can't you pin the problematic OVS packages via apt?

 

[udo]

PVE 6.3 can be fine for Nautilus -> Octopus, but for 6 -> 7 you need latest 6.4, so I'd recommend updating to that now already, a full reboot isn't a hard requirement if you plan to go to 7.x directly afterwards.


Yes, you can (and even must) upgrade to octopus before starting out the upgrade to Proxmox VE 7.x.

Hi,
sure - I mean the upgrade to octupus before update pve6.x to pve6.4

Can't you pin the problematic OVS packages via apt?

that's an good idea… I will try this way.

Udo

 

[udo]

Hi,
works without issues to pin openvswitch and upgrade all other packages.

Udo