I've been migrating my containers and VMs to another node in preparation for repurposing the node they're currently running on. So far it's been going well using the built-in "migrate" option in the GUI, but I'm running into an issue with one last container. The output from the log is below... anyone have any suggestions?
2023-04-24 09:31:05 starting migration of CT 101 to node 'pve2' (192.168.0.234)
2023-04-24 09:31:05 volume 'Shared2:101/vm-101-disk-0.raw' is on shared storage 'Shared2'
2023-04-24 09:31:05 start replication job
2023-04-24 09:31:05 guest => CT 101, running => 0
2023-04-24 09:31:05 volumes =>
2023-04-24 09:31:06 (remote_prepare_local_job) no volumes specified
2023-04-24 09:31:06 end replication job with error: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
2023-04-24 09:31:06 ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
2023-04-24 09:31:06 aborting phase 1 - cleanup resources
2023-04-24 09:31:06 start final cleanup
2023-04-24 09:31:06 ERROR: migration aborted (duration 00:00:01): command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
TASK ERROR: migration aborted
The root disk for this container has already been migrated to "Shared2," which is a directory under the ZFS pool on node2. This same migration strategy (moving the root disk first, then migrating the system) has worked for the others but this one is being stubborn.
2023-04-24 09:31:05 starting migration of CT 101 to node 'pve2' (192.168.0.234)
2023-04-24 09:31:05 volume 'Shared2:101/vm-101-disk-0.raw' is on shared storage 'Shared2'
2023-04-24 09:31:05 start replication job
2023-04-24 09:31:05 guest => CT 101, running => 0
2023-04-24 09:31:05 volumes =>
2023-04-24 09:31:06 (remote_prepare_local_job) no volumes specified
2023-04-24 09:31:06 end replication job with error: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
2023-04-24 09:31:06 ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
2023-04-24 09:31:06 aborting phase 1 - cleanup resources
2023-04-24 09:31:06 start final cleanup
2023-04-24 09:31:06 ERROR: migration aborted (duration 00:00:01): command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve2' root@192.168.0.234 -- pvesr prepare-local-job 101-0 --last_sync 0' failed: exit code 255
TASK ERROR: migration aborted
The root disk for this container has already been migrated to "Shared2," which is a directory under the ZFS pool on node2. This same migration strategy (moving the root disk first, then migrating the system) has worked for the others but this one is being stubborn.