Hi,
I set up my cluster to do fencing and I activated HA.
My first problem is that when I do a clean shutdown from the web interface of a VM or a CT, proxmox restart it automatically right after.
This forces me to remove the VM from the HA list, turn off the VM, do my work and then reactivate the HA.
Isn't proxmox able to see the difference between a crash and a clean shutdown or did I do domething wrong with my confirguration?
My second problem is more critical. Each time I do an update of the cluster.conf proxmox move all my HA VMs and CTs from a node to another even if everything is already running. This problem appears when I change de cluster.conf directly on the server (using the folowing method https://pve.proxmox.com/wiki/Fencing) or when I change it from the HA tab on the web GUI.
This problem is critical because when proxmox change from a node to another there is a break of a few seconds or minutes per VM/CT.
Moreover my first problem makes my second bigger. Each time I need to turn off a VM/CT I need to update the cluster.conf file and each time I do it proxmox restart everything and move it from a node to another.
In conclusion, in my case, the HA option of proxmox brings unavailability which makes me think that I did something wrong somewhere.
Here is my cluster.conf file (some informations have been changed or deleted but nothing useful):
I set up my cluster to do fencing and I activated HA.
My first problem is that when I do a clean shutdown from the web interface of a VM or a CT, proxmox restart it automatically right after.
This forces me to remove the VM from the HA list, turn off the VM, do my work and then reactivate the HA.
Isn't proxmox able to see the difference between a crash and a clean shutdown or did I do domething wrong with my confirguration?
My second problem is more critical. Each time I do an update of the cluster.conf proxmox move all my HA VMs and CTs from a node to another even if everything is already running. This problem appears when I change de cluster.conf directly on the server (using the folowing method https://pve.proxmox.com/wiki/Fencing) or when I change it from the HA tab on the web GUI.
This problem is critical because when proxmox change from a node to another there is a break of a few seconds or minutes per VM/CT.
Moreover my first problem makes my second bigger. Each time I need to turn off a VM/CT I need to update the cluster.conf file and each time I do it proxmox restart everything and move it from a node to another.
In conclusion, in my case, the HA option of proxmox brings unavailability which makes me think that I did something wrong somewhere.
Here is my cluster.conf file (some informations have been changed or deleted but nothing useful):
<?xml version="1.0"?>
<cluster config_version="115" name="***">
<cman keyfile="/var/lib/pve-cluster/corosync.authkey"/>
<fencedevices>
<fencedevice agent="fence_server" ipaddr="***.***.***.***" name="fence_server_virt1" power_wait="5"/>
<fencedevice agent="fence_server" ipaddr="***.***.***.***" name="fence_server_virt2" power_wait="5"/>
<fencedevice agent="fence_server" ipaddr="***.***.***.***" name="fence_server_virt3" power_wait="5"/>
</fencedevices>
<clusternodes>
<clusternode name="virt1" nodeid="1" votes="1">
<fence>
<method name="1">
<device name="fence_server_virt1"/>
</method>
</fence>
</clusternode>
.
. /** SAME here for the two others nodes **/
.
</clusternodes>
<rm>
<pvevm autostart="1" vmid="125"/>
.
. /**list of VMs/CTs
.
<pvevm autostart="1" vmid="386"/>
</rm>
</cluster>
Last edited: