Public bug reported:
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@lucid-test-lp
(/dev/console) at 4:23 ...
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-upgrades: * Asking all remaining processes to
terminate...
...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
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819621
Title:
container start failure after calling poweroff -n
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
