Public bug reported:
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.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1331930
Title:
quota-update and show succeeds for invalid tenant
Status in OpenStack Compute (Nova):
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1331930/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
