After PVE upgrade to 9.2.5 I cannot more migrate VM

[FrancisS]

After the PVE upgrade 9.2.5 I cannot migrate VM.

I have the message "Cannot migrate vm because ha resource vm:XXX is no-allowed on the selected target node"

l have also some times the message "Cannot migrate conntrack state, target node is lacking support. Active network connections might get dropped"

# pveversion -v
proxmox-ve: 9.2.0 (running kernel: 7.0.14-6-pve)
pve-manager: 9.2.5 (running version: 9.2.5/20242970da7fbcef)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0.14-6-pve-signed: 7.0.14-6
proxmox-kernel-7.0: 7.0.14-6
proxmox-kernel-7.0.14-5-pve-signed: 7.0.14-5
ceph: 19.2.3-pve4
ceph-fuse: 19.2.3-pve4
corosync: 3.1.10-pve3
criu: 4.1.1-1
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.18
libpve-guest-common-perl: 6.0.4
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.6
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.6
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-2
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.2.3-1
proxmox-backup-restore-image: 1.0.0
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.7
proxmox-widget-toolkit: 5.2.6
pve-cluster: 9.1.6
pve-container: 6.1.11
pve-docs: 9.2.3
pve-edk2-firmware: not correctly installed
pve-firewall: 6.0.5
pve-firmware: 3.18-5
pve-ha-manager: 5.2.4
pve-i18n: 3.9.0
pve-qemu-kvm: 11.0.2-1
pve-xtermjs: 6.0.0-2
qemu-server: 9.2.0
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2

I removed the VM from HA, for the migrate I have no error message, add VM to HA with "affinity node" (on one node no strict) i have the error message.

If I select 2 nodes for the "affinity node" I have no error message.... this is new ???

Best regards.
Francis

 

[dakralex]

Hi!

I removed the VM from HA, for the migrate I have no error message, add VM to HA with "affinity node" (on one node no strict) i have the error message.

If I understand your description correctly, this is expected behavior.

As HA resources are "failback" by default and the HA resource is in a non-strict node affinity rule, the HA Manager does not allow the migration. This is because the HA resource would be moved immediately back to the one node in the node affinity rule by the HA Manager as "failback" is enabled.

Failback in this sense means that the HA resource should always move to the highest-priority node, that is available according to the node affinity rules. Since the non-strict node affinity rule specifies only one node, which is then the only available highest-priority node, it will always move back there.

This was added as a recent change as part of BZ 1497 [0], which prevents violations of node affinity rules before the migration took place, similar to the resource affinity rules.

[0] https://bugzilla.proxmox.com/show_bug.cgi?id=1497

 

[FrancisS]

Hi,

Thank you, I understand the change.

Best regards.
Francis