touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #116803
[Bug 1242074] Re: lxc-ls shows wrong status
** Changed in: lxc (Ubuntu Precise)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074
Title:
lxc-ls shows wrong status
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Precise:
Invalid
Status in lxc source package in Quantal:
Won't Fix
Status in lxc source package in Raring:
Won't Fix
Status in lxc source package in Saucy:
Fix Released
Status in lxc source package in Trusty:
Fix Released
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/$name link must be a symbolic link to /var/lib/lxc/$name/config)
==========================
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions