interuppting lxc-clone can destroy source container
Bug #1285850 reported by
Kapil Thangavelu
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Vivid |
Won't Fix
|
Undecided
|
Unassigned | ||
Wily |
Won't Fix
|
Undecided
|
Unassigned | ||
Xenial |
Expired
|
High
|
Unassigned |
Bug Description
ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen containers on demand, but if i ctrl-c interuppt the operation, i've seen a few cases where it will destroy the source container (using snapshots and btrfs)
$ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
ctrl-c
the source container's rootfs directory goes missing, and only a rootfs.hold file remains in place.
btrfs subvolume list shows nothing for the missing container rootfs as well.
lxc-version -> 1.0.0.alpha1
Changed in lxc: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: patch |
no longer affects: | lxc |
Changed in lxc (Ubuntu): | |
importance: | Undecided → High |
Changed in lxc (Ubuntu Xenial): | |
importance: | Undecided → High |
To post a comment you must log in.
same problem doing an aufs snapshot container deletion (lxc daily ppa) on an interuppted clone . this one was a bit more odd
sudo lxc-destroy -n argo-m3 rmdir_onedev: failed to delete /var/lib/ lxc/precise- base/rootfs
lxc_container: _recursive_
lxc_container: Error destroying rootfs for argo-m3
Destroying argo-m3 failed
not sure why its trying to delete a different container root, hallyn pointed out there's probably an issue updating the container config rootfs pointer to late in the clone process leading to this issue.