Maintenance mode: no bulk migrate after use

[inno-forum]

I would like to use the maintenance mode.

2 Proxmoxs

• I enable the maintenance mode on Proxmox1.
• VMs are migrated to Proxmox 2
• I install the updates on Proxmox1
• I reboot Proxmox 1
• after some seconds, Proxmox tries to migrate all VM to Proxmox 1. This does not work because of reboot.
• After that, Proxmox1 always comes in maintenance mode.
• I disable the maintenance mode, but the VMs stay on Proxmox2 and I have to migrate them manually.

The expected behaviour would be that the VMs are automatically migrated to Proxmox 1.

 

[t.lamprecht]

2 Proxmoxs

Please note that in general the maintenance mode is currently done by the HA stack, and the HA stack recommends three nodes as minimum. But I guess that you have also a QDevice as third cluster vote setup, as otherwise self-fencing would trigger?

after some seconds, Proxmox tries to migrate all VM to Proxmox 1. This does not work because of reboot.

What do you mean, they immediately move over again after Proxmox1 boots up again?
This might be a bug that is already fixed pve-ha-manager version 3.6.1, but that version is not yet rolled out to the enterprise repository; so if you use that repo it might be indeed unexpected behavior.
You could temporarily add the no-subscription repository, then do:

# refresh package index:
apt update

# pull in only the HA manager upgrade
apt install pve-ha-manager

# now disable no-subscription repository again, after that refresh the index again
apt update

Otherwise waiting until next week should be enough, the HA manager package was long enough out there without any regression reported, so we'll move it to the enterprise repository soon anyway.

 

[inno-forum]

Please note that in general the maintenance mode is currently done by the HA stack, and the HA stack recommends three nodes as minimum. But I guess that you have also a QDevice as third cluster vote setup, as otherwise self-fencing would trigger?


What do you mean, they immediately move over again after Proxmox1 boots up again?
This might be a bug that is already fixed pve-ha-manager version 3.6.1, but that version is not yet rolled out to the enterprise repository; so if you use that repo it might be indeed unexpected behavior.
You could temporarily add the no-subscription repository, then do:

# refresh package index:
apt update

# pull in only the HA manager upgrade
apt install pve-ha-manager

# now disable no-subscription repository again, after that refresh the index again
apt update

Otherwise waiting until next week should be enough, the HA manager package was long enough out there without any regression reported, so we'll move it to the enterprise repository soon anyway.

We have 5 Nodes.
But in this Case, Proxmox1 and 2 belong to a restricted HA Group.

What do you mean, they immediately move over again after Proxmox1 boots up again?

yes.

This might be a bug that is already fixed pve-ha-manager version 3.6.1, but that version is not yet rolled out to the enterprise repository; so if you use that repo it might be indeed unexpected behavior.

Thanks a lot, I will wait the update and I will try again.

Great job

 

[rebootnz]

The Maintenace mode needs to be an option in the GUI. Having the option in CLI is great if you are scripting things.

But to get Proxmox more mainstream than having the option in the GUI to enable Maintenace mode is really required. It shouldn't be that hard to have it added to GUI.

Can this be added to the GUI?
If So any idea when.