lxc-ls shows wrong status
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Won't Fix
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
=======
SRU Justification:
1. Impact: standard lxc-tools do not work (transparently) with autostarted containers. Importantely, a duplicate container can be started.
2. Development fix: make sure to start containers (in lxc-instance) such that their command sockets are not in an "anonymous" lxcpath.
3. Stable fix: same as development fix.
4. Test case: Create an autostart container; start it with lxc-instance; look for it with lxc-ls.
5. Regression potential: Incorrectly setup autostart containers may no longer start with a fix. (the /etc/autostart/
=======
I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines.
as you can see my output for jenkins is "stopped", but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change.
# lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART
-------
jenkins STOPPED - - NO
php-54-32 STOPPED - - NO
test STOPPED - - NO
description: | updated |
Changed in lxc (Ubuntu Precise): | |
status: | Confirmed → Invalid |
Thanks for submitting this bug. Can you confirm whether the jenkins
machine was auto-started by lxc-instance? If not, can you please
run 'apport-collect 1242074' to have apport upload more information,
and tell us the path and type of container, and how you created and started
it?
status: incomplete