Proxmox cluster having a CARP messing with migration

spleenftw

Member
Oct 6, 2023
76
1
13
hello, i have a 3 node cluster.

pivoine (10.100.3.101)
petunia (10.100.3.102)
dahlia (10.100.3.103)

There's a CARP shared between the 3 nodes 10.100.3.100.

Migration worked flawlessly :

Code:
root@petunia:/var/log/pve/tasks# grep -r "qmigrate" /var/log/pve/tasks/ | grep "OK"
/var/log/pve/tasks/index:UPID:petunia:001C3E7C:0116FF23:6914A3A2:qmigrate:20023:root@pam: 6914A3A8 OK
/var/log/pve/tasks/index:UPID:petunia:001C559E:0117DDD0:6914A5DC:qmigrate:20023:root@pam: 6914A5E2 OK
root@petunia:/var/log/pve/tasks# date -d @$((0x6914A3A8))
date -d @$((0x6914A5E2))
Wed Nov 12 04:11:36 PM CET 2025
Wed Nov 12 04:21:06 PM CET 2025


but now, if I try to migrate a vm :
Code:
TASK ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=petunia' -o 'UserKnownHostsFile=/etc/pve/nodes/petunia/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@10.100.2.102 pvecm mtunnel -migration_network 10.100.4.102/24 -get_migration_ip' failed: exit code 255


I dont understand what's going on ?
 
Last edited: