container reboot patch broke clean lxc-execute exits
Bug #927863 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Serge Hallyn |
Bug Description
When lxc-execute exits 0, lxc currently errors out because there was no signal indicating type of reboot. Fix that.
Related branches
Changed in lxc (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
Changed in lxc (Ubuntu): | |
importance: | Medium → High |
To post a comment you must log in.
This bug was fixed in the package lxc - 0.7.5-3ubuntu18
---------------
lxc (0.7.5-3ubuntu18) precise; urgency=low
* lxcguest. lxcguest. upstart: emit the net-device-up IFACE=lo event, so lxc-execute- reboot. patch: fix bad handling of 'exit 0' for lxcguest. lxcmount. upstart: add '--no-wait' to emit to make sure we init-ignore- shm.patch: if lxc-init can't mount /dev/shm, don't
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP: #924337)
* 0034-fix-
lxc-execute introduced with the container reboot handling. (LP: #927863)
* debian/
don't wait for the event to be processed.
* 0035-lxc-
fail on account of that. (LP: #927883)
* debian/lxc.init: if the network is already up, exit before setting the
trap EXIT.
-- Serge Hallyn <email address hidden> Mon, 06 Feb 2012 17:37:37 -0600