corosync update reboot

A

Ashley

Member
Jun 28, 2016
267
15
18
35
Recently been trying out HA in Proxmox, just run an apt-get dist-upgrade on one node, this had an update for corosync causing the node to be fenced (rebooted).

1/ I have done some searching on the forum and have found a reply stating to stop two services on the node in question before updating (I guess just starting these two services after is then fine)

2/ Is there any plans to add something into the GUI to put a node into maintenance (or even something automatically during the apt-get dist-upgrade process) ?

3/ Is there any other / better method currently when doing upgrades that may contain an update for corosync?

Thanks
 
You could migrate VMs managed by HA to another node and then do the upgrade. Then no reboot will be applied.

Your 2) is a good point imho, would be nice to have kind of a maintenance mode in the GUI which disabled HA.
 
robhost said:
You could migrate VMs managed by HA to another node and then do the upgrade. Then no reboot will be applied.
Your 2) is a good point imho, would be nice to have kind of a maintenance mode in the GUI which disabled HA.
Click to expand...
Do this here by set the "nofailback option" on the concerned HA-Groups.
 
fireon said:
Do this here by set the "nofailback option" on the concerned HA-Groups.
Click to expand...

I understood this was still a VM moving to another node, but this will also stop a node from powering off if corosync does not respond?

I know they may sound the same just wanted to make sure!
 
Ashley said:
I understood this was still a VM moving to another node, but this will also stop a node from powering off if corosync does not respond?
Click to expand...
Hmm, ok, if it corosync not responding i think this is another problem, never had this before, not turning an update. A test in laboratory will be interesting.

Maybe some a Staff Member can help us to give an answer to this question.
 
Thats the best solution, indeed. But we have some clusters with mixed "HA" and "non HA" VMs where it's not possible to migrate all VMs due to the lack of free RAM on the other node(s) ;)

So we only do migrate the HA VMs before upgrading the PVE packages, which works just fine.
 
fireon said:
Ok, i never did this in this way. On every maintenance i migrate all VM's to an other node. Then i do the update.
Click to expand...

Fully understand about maintenance, and yes if I am doing anything more than a "apt-get dist-upgrade" then I would remove all VM's, but when applying updates that have no requirement for a reboot of the node so can be done live, if their is an update for the corosync package, this obviously causes the service to get restarted, causing the node to be fenced and rebooted.
 
Ashley said:
Fully understand about maintenance, and yes if I am doing anything more than a "apt-get dist-upgrade" then I would remove all VM's, but when applying updates that have no requirement for a reboot of the node so can be done live, if their is an update for the corosync package, this obviously causes the service to get restarted, causing the node to be fenced and rebooted.
Click to expand...
Yes! I'am agree with. Should work... hmm
 
Was a bug/feature:
Code: 
corosync-pve (2.4.2-2~pve4+1) unstable; urgency=medium
  * also restart when switching from old to new upgrade behaviour
 -- Proxmox Support Team <support@proxmox.com>  Wed, 8 Mar 2017 11:25:48 +0100
corosync-pve (2.4.2-2~pve4) unstable; urgency=medium
  * restart corosync.service on upgrades instead of stop-wait-start
 -- Proxmox Support Team <support@proxmox.com>  Tue, 7 Mar 2017 15:22:47 +0100
 
You must log in or register to reply here.
Top Bottom