Can't migrate stopped HA CT

[aTan]

Hi. When I try to migrate stopped CT from webgui I get this error:

Executing HA migrate for CT 1000 to node prox1
Trying to migrate pvevm:1000 to prox1...Temporary failure; try again
TASK ERROR: command 'clusvcadm -M pvevm:1000 -m prox1' failed: exit code 250

When I try to do it manually with -r it works fine. But from webgui it migrates CTs only with -M parameter which fails.

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

 

[Toshik]

It seems that stopped HA VM goes to "disabled" state and cannot be operated by GUI.

Try to execute

clusvmadm -d [COLOR=#333333][FONT=Verdana]pvevm:1000[/FONT][/COLOR] && clusvmadm -e [COLOR=#333333][FONT=Verdana]pvevm:1000[/FONT][/COLOR]

then use GUI to migrate VM

 

[aTan]

Thank you for your reply. -d parameter is good for resetting of the "failed" state, but mentioned error doesn't break the service. -e parameter will start the service and it will start the CT. But I need to migrate it when it is stopped (not running). When I just shut it down, HA will start it automatically back. The problem of the gui is that it uses -M parameter for migrating when Online is unchecked. Normally it would be enough to have an option "Relocate" in the gui, so it uses -r parameter for started CTs. Then it will shut CT down, move to another node and start it there. And it works fine from a console. Or at least it could use -r when Online is unchecked.

 

[tom]

If you use HA, the VM/CT runs always. If you want to move it to another node, just do a online migration.

In your case, its seems you do not want a running VM/CT. So just remove the CT/VM from HA - you can do this via GUI. and enable again if you want HA again.

 

[aTan]

I do want a running CT with HA, but not during a migration. The reason is quite simple. I use OpenVZ over GFS2. I know it is not supported by Proxmox, but it works flawless until live migration is used (because of a bug in OpenVZ, it fails to make a checkpoint on GFS2). The same problem occurs when I try to reboot a node with running CTs, Proxmox tries to migrate CTs online and fails leaving HA broken (all services/CTs are in "failed" state). So it is not just about me not wanting to use online migration, but about me not able to use it. There is no any possibility to disable online migration in HA (eg with <pvevm vmid="1000" migrate="relocate"> in cluster.conf, but now it knows only "online" and "pause") in Proxmox and use only offline relocation (clusvcadm -r) during migration which works well with GFS2. Even Migrate with Online unchecked uses clusvmadm -M.

 

[Toshik]

I use OpenVZ over GFS2. I know it is not supported by Proxmox, but it works flawless until live migration is used (because of a bug in OpenVZ, it fails to make a checkpoint on GFS2)

BTW - my CTs migrates over GFS2 on DRBD without any problems, It just "hangs" for a while on quota assigning, but all works.

 

[aTan]

I use external raid connected to both hosts by FC. Then I have cLVM on it and GFS2 mounted on both hosts. DRBD would unnecessary double diskspace usage. Everything works stable except live migration.