quota-update and show succeeds for invalid tenant
Bug #1331930 reported by
Tim Bell
This bug report is a duplicate of:
Bug #1118066: Nova should confirm quota requests against Keystone.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Abhishek Chanda | ||
Bug Description
The nova quota-update and quota-show commands do not produce an error when an invalid tenant is provided.
nova quota-show --tenant 1234567890123456789
reports the default values (rather than that the tenant is not known)
nova quota-update --key-pairs 4 1234567890123456789
succeeds although the tenant does not exist. It creates a record in the quotas table which is therefore invalid.
There is also a corresponding risk when an admin puts the text name of a tenant that the value is considered as recorded but is actually not matching the tenant uuid in the quotas table.
This has been tested on Icehouse.
| Changed in nova: | |
| assignee: | nobody → Abhishek Chanda (abhishek-i) |
Revision history for this message
| Thang Pham (thang-pham) wrote | #1 |
To post a comment you must log in.
There is a blueprint for this already and pending approval: https:/