[Group.of.nepali.translators] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-12-02 Thread Launchpad Bug Tracker
[Expired for lxc (Ubuntu Xenial) because there has been no activity for
60 days.]

** Changed in: lxc (Ubuntu Xenial)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Expired
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Expired

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/ubuntu/+source/lxc/+bug/1285850/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-12-02 Thread Launchpad Bug Tracker
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lxc (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Expired
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Expired

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/ubuntu/+source/lxc/+bug/1285850/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-09-30 Thread Jon Grimm
Marked Vivid and Wily as Won't Fix as EOL releases.

** Changed in: lxc (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

** Changed in: lxc (Ubuntu Wily)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Incomplete
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Confirmed

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/ubuntu/+source/lxc/+bug/1285850/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp