Hi,
I'm running proxmox clusters since 2.0 and now am running 3.4
Am using failover domains and everything was working fine regarding failovers , usually when I want to do any node maintenance I stop rgmanager first on that node and cluster HA handles all the migrations AUTOMATICALLY to other nodes depending on the failover domains priorities and again this was always working like configured and once am done with the node maintenance I started rgmanager again and because I've nofailback=0 in cluster.conf all CTs are moved back to that node AUTOMATICALLY.
but now when I do the same scenario CTs are stopped normally on that node and not moved/migrated to other nodes as configured and when I start rgmanager service again they are started fine on the same node.
I'm not sure if this was changed after 3.2 release but is there a way to do the above scenario like before ?
Please advise and thanks in advance.
I'm running proxmox clusters since 2.0 and now am running 3.4
Code:
root@cluster2b8:~# pveversion -v
proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-43-pve)
pve-manager: 3.4-11 (running version: 3.4-11/6502936f)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-43-pve: 2.6.32-166
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-5
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-14
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@cluster2b8:~#Am using failover domains and everything was working fine regarding failovers , usually when I want to do any node maintenance I stop rgmanager first on that node and cluster HA handles all the migrations AUTOMATICALLY to other nodes depending on the failover domains priorities and again this was always working like configured and once am done with the node maintenance I started rgmanager again and because I've nofailback=0 in cluster.conf all CTs are moved back to that node AUTOMATICALLY.
but now when I do the same scenario CTs are stopped normally on that node and not moved/migrated to other nodes as configured and when I start rgmanager service again they are started fine on the same node.
I'm not sure if this was changed after 3.2 release but is there a way to do the above scenario like before ?
Please advise and thanks in advance.