[Bug 1242074] Re: lxc-ls shows wrong status

2015-11-09 Thread Stéphane Graber
** Changed in: lxc (Ubuntu Precise)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2014-12-04 Thread Rolf Leggewie
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.

** Changed in: lxc (Ubuntu Quantal)
   Status: Confirmed = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2014-02-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lxc (Ubuntu Quantal)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2014-02-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lxc (Ubuntu Raring)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2014-02-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lxc (Ubuntu Precise)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2014-02-12 Thread Stéphane Graber
Precise and Quantal are pre-1.0, were they actually affected by this
bug?

** Changed in: lxc (Ubuntu Raring)
   Status: Confirmed = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2013-11-04 Thread Serge Hallyn
This was fixed in saucy by the fix for 1244301

** Changed in: lxc (Ubuntu Saucy)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2013-10-21 Thread Serge Hallyn
** Also affects: lxc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Trusty)
   Importance: Medium
   Status: Triaged

** Also affects: lxc (Ubuntu Saucy)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Raring)
   Importance: Undecided
   Status: New

** Description changed:

- I just upgraded to ubuntu saucy and found a strange behaviour. The
- command lxc-ls doesn't show the correct status of running machines.
+ =
+ 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   STATEIPV4  IPV6  AUTOSTART
  -
  jenkinsSTOPPED  - - NO
  php-54-32  STOPPED  - - NO
  test   STOPPED  - - NO

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2013-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package lxc - 1.0.0~alpha2-0ubuntu3

---
lxc (1.0.0~alpha2-0ubuntu3) trusty; urgency=low

  * Fix syntax error in upstart job.
 -- Stephane Graber stgra...@ubuntu.com   Mon, 21 Oct 2013 18:51:36 -0400

** Changed in: lxc (Ubuntu Trusty)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1242074] Re: lxc-ls shows wrong status

2013-10-20 Thread Serge Hallyn
Drat my comment got lost.

The lxc-instance job ends up starting containers as 'anonymous'.  You
can see them using

  lxc-list -P /var/lib/lxc_anon

The autostart code is currently being reworked but I think this is worth
fixing in older releases.  It coudl be fixed in one of two ways - or
both:  the lxc-instance job could detect that linked file is a standard
container's config and start it that way (without specifying -f);  or
lxc-start could detect that the passed-in rcfile is a link to a standard
$lxcpath/$name/config, and not start the container anonymously.

** Changed in: lxc (Ubuntu)
   Importance: Undecided = Medium

** Changed in: lxc (Ubuntu)
   Status: Incomplete = Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242074

Title:
  lxc-ls shows wrong status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs