Hi Guys,
I'm trying to migrate running VM from NodeC to NodeD and have this error where atomic file exists on NodeD.
I double checked and there is NO file mentioned on NodeD.
Logs attached.
2025-12-01 14:51:40 use dedicated network address for sending migration traffic (10.10.10.4)
2025-12-01 14:51:41 starting migration of VM 103 to node 'NodeD-r3-s19' (10.10.10.4)
2025-12-01 14:51:41 starting VM 103 on remote node 'NodeD-r3-s19'
2025-12-01 14:51:44 [NodeD-r3-s19] close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists
2025-12-01 14:51:44 ERROR: online migrate failure - remote command failed with exit code 255
2025-12-01 14:51:44 aborting phase 2 - cleanup resources
2025-12-01 14:51:44 migrate_cancel
2025-12-01 14:51:45 ERROR: migration finished with problems (duration 00:00:05)
TASK ERROR: migration problems
netdev net0: not adding 'host_mtu' parameter for migration compat
/dev/rbd0
migration listens on unix:/run/qemu-server/103.migrate
No VM state set, removing left-over option 'runningmachine'
No VM state set, removing left-over option 'runningcpu'
TASK ERROR: close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists
root@NodeC-r3-s19:~# pvecm status
Cluster information
-------------------
Name: pve-a-waw
Config Version: 4
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Mon Dec 1 15:13:56 2025
Quorum provider: corosync_votequorum
Nodes: 4
Node ID: 0x00000003
Ring ID: 1.56
Quorate: Yes
Votequorum information
----------------------
Expected votes: 4
Highest expected: 4
Total votes: 4
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.10.10.1
0x00000002 1 10.10.10.2
0x00000003 1 10.10.10.3 (local)
0x00000004 1 10.10.10.4
Best regards,
Mihoo
I'm trying to migrate running VM from NodeC to NodeD and have this error where atomic file exists on NodeD.
I double checked and there is NO file mentioned on NodeD.
Logs attached.
2025-12-01 14:51:40 use dedicated network address for sending migration traffic (10.10.10.4)
2025-12-01 14:51:41 starting migration of VM 103 to node 'NodeD-r3-s19' (10.10.10.4)
2025-12-01 14:51:41 starting VM 103 on remote node 'NodeD-r3-s19'
2025-12-01 14:51:44 [NodeD-r3-s19] close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists
2025-12-01 14:51:44 ERROR: online migrate failure - remote command failed with exit code 255
2025-12-01 14:51:44 aborting phase 2 - cleanup resources
2025-12-01 14:51:44 migrate_cancel
2025-12-01 14:51:45 ERROR: migration finished with problems (duration 00:00:05)
TASK ERROR: migration problems
netdev net0: not adding 'host_mtu' parameter for migration compat
/dev/rbd0
migration listens on unix:/run/qemu-server/103.migrate
No VM state set, removing left-over option 'runningmachine'
No VM state set, removing left-over option 'runningcpu'
TASK ERROR: close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists
root@NodeC-r3-s19:~# pvecm status
Cluster information
-------------------
Name: pve-a-waw
Config Version: 4
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Mon Dec 1 15:13:56 2025
Quorum provider: corosync_votequorum
Nodes: 4
Node ID: 0x00000003
Ring ID: 1.56
Quorate: Yes
Votequorum information
----------------------
Expected votes: 4
Highest expected: 4
Total votes: 4
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.10.10.1
0x00000002 1 10.10.10.2
0x00000003 1 10.10.10.3 (local)
0x00000004 1 10.10.10.4
Best regards,
Mihoo