[PVE-User] Container migration issue

Gustaf Ankarloo gankarloo at gmail.com
Fri Apr 7 23:28:19 CEST 2017


Hi.

Today after upgrading my pve cluster to 4.4-13/7ea56165
I'm no longer able to migrate containers.

more precise the container is migrated but not started on the new node.
If I start the container manually it works.

I use OVS


Error from the webgui
CT 106 - Migrate
Apr 07 23:14:04 shutdown CT 106
Apr 07 23:14:04 # lxc-stop -n 106 --timeout 180
Apr 07 23:14:05 # lxc-wait -n 106 -t 5 -s STOPPED
Apr 07 23:14:07 starting migration of CT 106 to node 'pve-2' (192.168.1.21)
Apr 07 23:14:07 volume 'DATA:106/vm-106-disk-1.raw' is on shared storage
'DATA'
Apr 07 23:14:07 start final cleanup
Apr 07 23:14:07 start container on target node
Apr 07 23:14:07 # /usr/bin/ssh -o 'BatchMode=yes' root at 192.168.1.21 pct
start 106
Apr 07 23:14:35 command 'systemctl start lxc at 106' failed: exit code 1
Apr 07 23:14:35 Job for lxc at 106.service failed. See 'systemctl status
lxc at 106.service' and 'journalctl -xn' for details.
Apr 07 23:14:35 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes'
root at 192.168.1.21 pct start 106' failed: exit code 255
Apr 07 23:14:35 ERROR: migration finished with problems (duration 00:00:31)
TASK ERROR: migration problems

CT 106 - Start
Job for lxc at 106.service failed. See 'systemctl status lxc at 106.service' and
'journalctl -xn' for details.
TASK ERROR: command 'systemctl start lxc at 106' failed: exit code 1


On the original node I find this in the ovs-vswitchd.log
2017-04-07T21:14:05.558Z|00030|netdev_linux|WARN|veth106i0: removing
policing failed: No such device
2017-04-07T21:14:05.562Z|00031|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
veth106i0 device failed: No such device
2017-04-07T21:14:05.564Z|00032|netdev_linux|WARN|ethtool command
ETHTOOL_GSET on network device veth106i0 failed: No such device
2017-04-07T21:14:05.568Z|00033|bridge|WARN|could not open network device
veth106i0 (No such device)

Which is strange, I would assume that the recieving node would try to add
the interface not the original.

And dmesg on the recieving node says this
[28546.765584] EXT4-fs warning (device loop1):
ext4_multi_mount_protect:337: Device is already active on another node.
[28546.765590] EXT4-fs warning (device loop1):
ext4_multi_mount_protect:337: MMP failure info: last update time:
1491599646, last update node: pve-1, last update device: loop1


Does any one have any suggestions on whats going on?
-- 
Best regards
Gustaf Ankarloo



More information about the pve-user mailing list