touch-packages team mailing list archive

[Serge Hallyn <1285850@xxxxxxxxxxxxxxxxxx>]

This was fixed by commit 5eea90e8505d9f336bb28379d8575be159fdd2e1, it
was github issue http://github.com/lxc/lxc/issues/694.

It needs to be SRUd somewhat urgently.


** Also affects: lxc (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

Status in lxc:
  Triaged
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Vivid:
  New
Status in lxc source package in Wily:
  New
Status in lxc source package in Xenial:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxc/+bug/1285850/+subscriptions