nova list's --tenant flag also requires --all-tenants
Bug #1185290 reported by
Aarti Kriplani
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Ghanshyam Mann |
Bug Description
When a user with admin access tries to list all instances that belong to a given tenant, it works only when the --all-tenant flag is passed.
For e.g. nova list --tenant 123456 --all-tenants 1
If you leave off the last "--all-tenants 1" flag, you get back an empty response body (with a 200 response)
The "--all-tenants 1" should not be required for the "--tenant" flag to function properly.
Changed in nova: | |
assignee: | nobody → Aarti Kriplani (aarti-kriplani) |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
tags: | added: api |
To post a comment you must log in.
I am not sure that I consider this a bug. Without --all-tenants=1, the code operates under your own tenant. That means that --tenant <foo> should really be a no-op without --all-tenants=1.
Others may disagree.