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

Bug #1514961 reported by Jeff Lane 
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Won't Fix
Undecided
Unassigned

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 |
+------+-------+------+------+-----------+-----------+
+------+-------+------+------+-----------+-----------+

Revision history for this message
Stéphane Graber (stgraber) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.