[PVE-User] HA migration behaviour vs. failures

[Dhaussy Alexandre]

I don't, that's why i added a status check in the code (see my first post.)

+    check_running($status);
+    exit(OCF_ERR_MIGRATE) if $status->{running};

Inspired from RedHat script (line 1043:/usr/share/cluster/vm.sh)

Why would you assume the opposite ?

Le 24/07/2014 20:45, Dietmar Maurer a écrit :
> If kvm migration command fails, how can you assume that the VM is still OK?
>
>
> Le 24/07/2014 14:15, Dhaussy Alexandre a écrit :
>>> In broad outline.
>>>
>>> With RedHat cluster :
>>> 1/ @node1: clusvcadm -M vm:foo -m node2 2/ @node2: kill the kvm/foo
>>> process 3/ @node1: clusvcadm fails with non-critical error (OCF code
>>> 150, see
>>> /usr/share/cluster/vm.sh)
>>>
>>> => You are happy and your VM is still in a good health.
>>>
>>> With Proxmox :
>>> 1/ @node1: clusvcadm -M pvevm:foo -m node2 2/ @node2: kill the kvm/foo
>>> process 3/ @node1: clusvcadm fails with code 1 (OCF_ERR_GENERIC),
>>> which ends up doing "clusvcadm -d pvevm:foo"
>>>
>>> => Your VM is dead.
>>>
>>> Regards,
>>> --
>>>
>>> Alexandre DHAUSSY
>>>
>>> Le 24/07/2014 12:49, Dietmar Maurer a écrit :
>>>
>>>>> Sorry for being a bit cheeky here, but why did you change the way
>>>>> RedHat cluster behaves with online migration
>>>> I am not aware that we changed that?
>>>>
>>>>
>>>>