Cephx Key Migration Procedure and Ceph 19.2 Squid Going EOL Soon

[shfp79]

You do not need to reboot the nodes, and NEVER use apt upgrade -> it can break your system. use dist-upgrade or full-upgrade

OK. Thank you very much for your input. Understood to never use simple apt upgrade

But the kernel would be also updated, so I think we have to restart the nodes on some point?

If I understood you correctly:
1) Install ALL updates directly on all three nodes with apt full-upgrade
2) Do the rolling restart of Ceph services
3) Do the key exchange
4) Let go all the errors and warnings regarding CephX authentication
5) Then I would restart the nodes? (because of the kernel updates from step 1)

Honestly, we're running PVE since years (12-13?) now and as I can remember we never bricked our systems with the simple apt upgrade but if you had bad experiences in the past then we should avoid that in the future. Thank you

 

[jsterr]

OK. Thank you very much for your input. Understood to never use simple apt upgrade

But the kernel would be also updated, so I think we have to restart the nodes on some point?

If I understood you correctly:
1) Install ALL updates directly on all three nodes with apt full-upgrade
2) Do the rolling restart of Ceph services
3) Do the key exchange
4) Let go all the errors and warnings regarding CephX authentication
5) Then I would restart the nodes? (because of the kernel updates from step 1)

Honestly, we're running PVE since years (12-13?) now and as I can remember we never bricked our systems with the simple apt upgrade but if you had bad experiences in the past then we should avoid that in the future. Thank you

Theoretically apt upgrade might refuse to install, remove, or replace package dependencies that Proxmox requires to function. Yes you can reboot at a different time. You also might need to move around some vms between hosts to "refresh" clients as the docs state.