I have a 3 node cluster, with HA configured for some of my VMs/LXCs.
Due to a reboot on 2 of these machines, one of my LXC containers is now stuck. The container CT101 is listed under
When I try starting the container, I immediately get a migration error:
Running
How can I fix this?
EDIT: Looks like it was as simple as moving the 101.conf file over to the other machine
Due to a reboot on 2 of these machines, one of my LXC containers is now stuck. The container CT101 is listed under
opti2-pve
while the data I believe is still on opti-pve
.When I try starting the container, I immediately get a migration error:
Code:
task started by HA resource agent
2022-11-26 15:29:00 starting migration of CT 101 to node 'opti-pve' (10.0.10.12)
2022-11-26 15:29:00 volume 'nas:101/vm-101-disk-0.raw' is on shared storage 'nas'
2022-11-26 15:29:00 found local volume 'local-lvm:vm-101-disk-0' (in current VM config)
2022-11-26 15:29:00 found local volume 'local-lvm:vm-101-disk-1' (in current VM config)
2022-11-26 15:29:01 ERROR: storage migration for 'local-lvm:vm-101-disk-1' to storage 'local-lvm' failed - no such logical volume pve/vm-101-disk-1
2022-11-26 15:29:01 aborting phase 1 - cleanup resources
2022-11-26 15:29:01 ERROR: found stale volume copy 'local-lvm:vm-101-disk-1' on node 'opti-pve'
2022-11-26 15:29:01 start final cleanup
2022-11-26 15:29:01 ERROR: migration aborted (duration 00:00:01): storage migration for 'local-lvm:vm-101-disk-1' to storage 'local-lvm' failed - no such logical volume pve/vm-101-disk-1
TASK ERROR: migration aborted
Running
lvdisplay
on opti-pve gives me the correct disk:
Code:
--- Logical volume ---
LV Path /dev/pve/vm-101-disk-1
LV Name vm-101-disk-1
VG Name pve
LV UUID OlgNn2-biL0-1Xzk-WzcN-UlF5-neKw-v230pt
LV Write Access read/write
LV Creation host, time opti-pve, 2022-11-08 10:56:25 +1100
LV Pool name data
LV Status available
# open 0
LV Size 20.00 GiB
Mapped size 67.37%
Current LE 5120
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:10
How can I fix this?
EDIT: Looks like it was as simple as moving the 101.conf file over to the other machine
Last edited: