** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications
This bug was fixed in the package lxc - 1.1.0~alpha2-0ubuntu2
---
lxc (1.1.0~alpha2-0ubuntu2) utopic; urgency=medium
* Cherry-pick usptream bugfix for lxc-usernic test.
-- Stephane Graber stgra...@ubuntu.com Thu, 02 Oct 2014 15:01:56 -0400
** Changed in: lxc (Ubuntu)
This bug was fixed in the package lxc - 1.1.0~alpha2-0ubuntu2
---
lxc (1.1.0~alpha2-0ubuntu2) utopic; urgency=medium
* Cherry-pick usptream bugfix for lxc-usernic test.
-- Stephane Graber stgra...@ubuntu.com Thu, 02 Oct 2014 15:01:56 -0400
** Changed in: lxc (Ubuntu)
** Tags added: ubuntu-engineering
** Changed in: juju-core
Importance: Medium = High
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
The fix for this is applied in lxc's git HEAD.
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
** Tags added: ubuntu-engineering
** Changed in: juju-core
Importance: Medium = High
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fix for this is applied in lxc's git HEAD.
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
Correct. Attached is a juju-deployer config that reproduces the issue
when used with the juju local provider and /var/lib/lxc in the host
backed onto btrfs. If you deploy it and run juju destroy-environment
--force -y local, it should fail.
This is because Ceph sees that /srv/ceph is on btrfs and
Correct. Attached is a juju-deployer config that reproduces the issue
when used with the juju local provider and /var/lib/lxc in the host
backed onto btrfs. If you deploy it and run juju destroy-environment
--force -y local, it should fail.
This is because Ceph sees that /srv/ceph is on btrfs and
To further clarify, this isn't a juju bug. lxc should be smart enough to
delete dependent subvolumes before it deletes the rootfs subvolume. I
took a stab at this over the weekend, but ran out of time.
btrfs_destroy(struct bdev *orig) is what you're after.
** Also affects: lxc (Ubuntu)
To be sure I understand, the issue is that inside your container you
created btrfs subvolumes (by using btrfs containers or manually using
btrfs subvolume create)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
To further clarify, this isn't a juju bug. lxc should be smart enough to
delete dependent subvolumes before it deletes the rootfs subvolume. I
took a stab at this over the weekend, but ran out of time.
btrfs_destroy(struct bdev *orig) is what you're after.
** Also affects: lxc (Ubuntu)
To be sure I understand, the issue is that inside your container you
created btrfs subvolumes (by using btrfs containers or manually using
btrfs subvolume create)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications about
20 matches
Mail list logo
