What's the actual, official way to reboot nodes in an HA-enabled cluster?

[DC-CA1]

packages are now on pve-no-subscription, please see the following extra information if you have been affected by a full-cluster-crash with the mentioned symptoms (one node rebooting/upgrading/restarting corosync -> cpg_join/cpg_send_message retry log entries followed by watchdog expiring on all nodes):

https://bugzilla.proxmox.com/show_bug.cgi?id=3672

for people who triggered this easily because of their particular load/network situation, it might be advisable to follow the following procedure to avoid triggering it again when installing the fixed versions:

stop the HA services (first LRM on all nodes, then CRM on all nodes - this disables HA, but also disarms the watchdog so you don't risk fencing)

then upgrade all nodes (this will automatically restart corosync, which will pick up the fixed libknet as well)

then start the HA services again (again first LRM on all nodes, then CRM) to re-enable HA features

hi fabian,
i seem to have faced the same situation here concerning the thread we are discussing . possible ?
https://forum.proxmox.com/threads/3...n-1000-email-in-5-minutes.122354/#post-531832

 

[DC-CA1]

Hi,

FYI: The "remove from group before reboot and re-add after" part may be obsoleted by using the "migrate" shutdown policy:
https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#_node_maintenance


No, that should be it and. fwiw, I use that all the time in my clusters. Maybe some other service or characteristic in the system interferes with the graceful shutdown.

Can you post the journal from such a shutdown, maybe we can figure something out from that?
Also, which Proxmox VE version are you using? pveversion -v

Hi Thomas

can you give me a quick advice on this topic :
https://forum.proxmox.com/threads/is-nodes-inside-a-ha-group-the-only-ones-to-fences.122428/

we faced a similar situation and are trying to see if we can '' half use HA '' but not been scared of a HA bug can crash 15 nodes..