lucid container start failure after calling lxc-stop (fails across reboots)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
The following recipe appears to reliably nuke a lxc i386 lucid container running on a oneiric amd64 host:
lxc-start -n <name>
(login)
sudo poweroff -n
- hangs
in another terminal
sudo lxc-stop -n <name>
then
sudo lxc-start -n <name>
shows
sudo lxc-start -n lucid-test-lp
init: plymouth-splash main process (170) terminated with status 2
init: plymouth main process (7) killed by ABRT signal
init: ssh main process (37) terminated with status 255
the output from poweroff is this:
Broadcast message from robertc@
The system is going down for power off NOW!
robertc@lucid-test-lp:~$ init: tty4 main process (225) killed by TERM signal
init: tty2 main process (226) killed by TERM signal
init: tty3 main process (228) killed by TERM signal
init: tty1 main process (241) killed by TERM signal
init: console main process (2534) killed by TERM signal
Checking for running unattended-
...done.
* All processes ended within 1 seconds....
...done.
* Deconfiguring network interfaces...
...done.
* Deactivating swap...
...fail!
* Unmounting weak filesystems...
...done.
mount: / is busy
* Will now halt
Related branches
Changed in lxc (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Further investigation shows that just: /dev.launchpad. net/Running/ LXC)
logging into the new container
installing some packages (see https:/
and calling lxc-stop from another terminal
will cause this.
Am progressing with shorter and shorter tests