Per-userness of "nova list" is confused
Bug #916219 reported by
David Kranz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Dan Prince |
Bug Description
Most of the "nova *-list" commands are with respect to a given user. "nova list" is so documented but instead shows the vms of multiple users. However, "nova show xx" only lets you see details of your own vms. If you provide xx as the id of another user's vm as shown by "nova list" then you get the following strange error, regardless of which xx you use:
No image with a name or ID of '2' exists.
This was while running nova packages built from a recent diablo-stable, using
python-novaclient 2.6.4~bzr112-
The same thing happens with the most recent nova client from github.
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
status: | Triaged → In Progress |
Changed in nova: | |
milestone: | none → essex-4 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
It seems that my diablo-stable was overwritten by a new oneiric nova update that still does not contain any of the diablo-stable fixes. After repairing that the strange error no longer occurs. But 'nova list' still shows all vms.