new-vm --replace stops on a hand-deleted system disk and leaves the domain defined #79
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/nexus#79
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
new-vm --replaceremoves the old machine withvirsh undefine --storage vda, which stops withstorage volume is not managed by libvirtwhen the disk image at that path has been deleted by hand. The domain is still defined, so a plainprovision-vmrefuses too, and the operator is stuck between two refusals until theyvirsh undefinethe domain themselves andvirsh pool-refresh defaultso libvirt forgets the stale volume.A hand-deleted image is a normal thing to find after an operator cleaned up a disk by path, which is the first thing they try when the disk is the thing they want gone.
Proposal: when the volume
--storagenames no longer exists on disk,--replaceundefines the domain without--storageand refreshes the pool, then proceeds; a volume that exists keeps the current path. Both branches keep the existing refusals for a data disk atvda.Found during the public install walk while resetting the laptop between runs.