touch-packages team mailing list archive

[Stéphane Graber <stgraber@xxxxxxxxxxxx>]

That's by design, none of the lxc-test-* binaries clean after themselves
on failure so that the developer running them can go inspect the
remnants to understand what's actually happened.

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

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

Title:
  lxc-test-checkpoint-restore doesn't clean up after itself and I am
  unable to re-run it

Status in lxc package in Ubuntu:
  Won't Fix

Bug description:
  I ran lxc-test-checkpoint-restore and it failed.  So I decided to try
  one additional attempt to verify the failure.  However now I am unable
  to re-run the test because apparently the container already exists
  (previous test did not clean up after itself), however, lxc list does
  not show any running containers...

  ubuntu@xwing:~$ lxc list
  +------+-------+------+------+-----------+-----------+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +------+-------+------+------+-----------+-----------+
  +------+-------+------+------+-----------+-----------+
  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  Container already exists
  Failed creating container
  ubuntu@xwing:~$ sudo lxc list
  +------+-------+------+------+-----------+-----------+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +------+-------+------+------+-----------+-----------+
  +------+-------+------+------+-----------+-----------+

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