touch-packages team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

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 makes use of
it.

ubuntu@vagrant-local-machine-1:~$ mount
/dev/sda2 on / type btrfs (rw)

So you'll end up with lots of snapshots created by Ceph inside LXC.
These will be visible by running `btrfs subvolume list /var/lib/lxc` in
the host:

(.venv-ubuntu)vagrant@vagrant-ubuntu-trusty-64:~$ sudo btrfs subvolume list /var/lib/lxc
ID 256 gen 9268 top level 5 path @lxc
ID 257 gen 8126 top level 256 path juju-precise-template/rootfs
ID 285 gen 8006 top level 256 path juju-trusty-template/rootfs
ID 762 gen 9208 top level 256 path vagrant-local-machine-25/rootfs
ID 763 gen 9208 top level 256 path vagrant-local-machine-26/rootfs
ID 764 gen 9208 top level 256 path vagrant-local-machine-27/rootfs
ID 925 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/current
ID 934 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/current
ID 944 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/current
ID 951 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4426
ID 954 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4483
ID 957 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4767
ID 958 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5753
ID 959 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4845
ID 960 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5754

** Attachment added: "object-storage.yaml"
   https://bugs.launchpad.net/juju-core/+bug/1307215/+attachment/4154884/+files/object-storage.yaml

-- 
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/1307215

Title:
  destroy-environment fails to clear lxc containers

Status in juju-core:
  Triaged
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Running destroy-environment with --force happily cleans up evan-local-
  machine-1, but fails to remove 2 or 3. I think this is what led to bug
  1303778 for me.

    % juju destroy-environment local --force
  WARNING! this command will destroy the "local" environment (type: local)
  This includes all machines, services, data and other resources.

  Continue [y/N]? y
  [sudo] password for evan:
  ERROR failed to destroy lxc container: error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-2; Destroying evan-local-machine-2 failed
  ERROR error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-2; Destroying evan-local-machine-2 failed
  ERROR exit status 1

   % sudo lxc-ls -f
  NAME                   STATE    IPV4  IPV6  AUTOSTART
  -----------------------------------------------------
  evan-local-machine-2   STOPPED  -     -     YES
  evan-local-machine-3   STOPPED  -     -     YES
  juju-precise-template  STOPPED  -     -     NO

    % juju destroy-environment local --force
  WARNING! this command will destroy the "local" environment (type: local)
  This includes all machines, services, data and other resources.

  Continue [y/N]? y
  ERROR failed to destroy lxc container: error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-3; Destroying evan-local-machine-3 failed
  ERROR error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-3; Destroying evan-local-machine-3 failed
  ERROR exit status 1

   % sudo lxc-ls -f
  NAME                   STATE    IPV4  IPV6  AUTOSTART
  -----------------------------------------------------
  evan-local-machine-2   STOPPED  -     -     YES
  evan-local-machine-3   STOPPED  -     -     YES
  juju-precise-template  STOPPED  -     -     NO

    % juju destroy-environment local --force
  WARNING! this command will destroy the "local" environment (type: local)
  This includes all machines, services, data and other resources.

  Continue [y/N]? y

   % sudo lxc-ls -f
  NAME                   STATE    IPV4  IPV6  AUTOSTART
  -----------------------------------------------------
  evan-local-machine-2   STOPPED  -     -     YES
  evan-local-machine-3   STOPPED  -     -     YES
  juju-precise-template  STOPPED  -     -     NO

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1307215/+subscriptions