lxc-ls doesn't show nested containers when using an alternate lxc path

Bug #1177412 reported by Stéphane Graber
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Fix Released
Medium
Stéphane Graber
Raring
Won't Fix
Medium
Stéphane Graber

Bug Description

== Rationale ==
"lxc-ls -P /some/path --fancy --nesting" fails to show nested containers and running container information.
This is caused by the lack of lxcpath awareness in the get_ips() API call and by the NESTED environment variable containing the host's lxcpath and not the container's default lxcpath.

== Test case ==
1) Create a container with a sub-container in it
2) Move the container to an alternate path, let's say /tmp/lxc
3) Start it with: lxc-start -P /tmp/lxc -n container -d
4) List the containers: lxc-ls --fancy --nesting -P /tmp/lxc

Expected output is the main container with the sub-container under it, both of which with their status and IP addresses.

== Regression potential ==
This slightly changes the behaviour of lxc-ls in that in the past it'd successfully list sub-containers if they had the exact same custom lxcpath as the host, however this is very unusual and not something upstream feels should be supported at this time.
Instead it's expected that the container containing sub-containers in the default lxcpath will be much more common.

As the get_ips() call was preventing those containers to show up anyway, it's unlikely anyone will notice the small change in behaviour.

Changed in lxc (Ubuntu):
status: New → Triaged
Changed in lxc (Ubuntu Raring):
status: New → Triaged
Changed in lxc (Ubuntu):
importance: Undecided → Medium
Changed in lxc (Ubuntu Raring):
importance: Undecided → Medium
assignee: nobody → Stéphane Graber (stgraber)
Changed in lxc (Ubuntu):
assignee: nobody → Stéphane Graber (stgraber)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc - 0.9.0-0ubuntu4

---------------
lxc (0.9.0-0ubuntu4) saucy; urgency=low

  * Fix lxc-list crashing when passed --nesting with nested containers.
    (LP: #1177408)
  * Fix lxc-ls to show nested containers when using alternate lxcpath.
    (LP: #1177412)
  * Fix python3 API bug leading to parameter corruption in create and start.
    (LP: #1177400)
 -- Stephane Graber <email address hidden> Tue, 07 May 2013 10:48:40 -0400

Changed in lxc (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Dave Walker (davewalker) wrote : Please test proposed package

Hello Stéphane, or anyone else affected,

Accepted lxc into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/lxc/0.9.0-0ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in lxc (Ubuntu Raring):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Stéphane Graber (stgraber) wrote :

Looks good here.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in lxc (Ubuntu Raring):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.