yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32500
[Bug 1031139] [NEW] quota-show should return error for invalid tenant id
You have been subscribed to a public bug:
quota-show does not handle alternatives for tenant_id as expected
ENV: Devstack trunk (Folsom) / nova
d56b5fc3ad6dbfc56e0729174925fb146cef87fa , Mon Jul 30 21:59:56 2012
+0000
I'd expect the following command to work as $ env | grep TENANT ->
OS_TENANT_NAME=demo
$ nova --debug --os_username=admin --os_password=password quota-show
usage: nova quota-show <tenant_id>
error: too few arguments
I'd also expect the following to work:
$ nova --debug --os_username=admin --os_password=password quota-show --os_tenant_name=demo
usage: nova quota-show <tenant_id>
error: too few arguments
What is more awesome, if in the event that I do provide the wrong tenant_id, it proceeds to use OS_TENANT_NAME returning those results:
$nova --debug --os_username=admin --os_password=password quota-show
gggggggggggggggggggggggggggggggggg
REQ: curl -i http://10.1.11.219:8774/v2/04adebe40d214581b84118bcce264f0e
/os-quota-sets/ggggggggggggggggggggggggggggggggggg -X GET -H "X-Auth-
Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token: 10bd3f948df24039b2b88b98771b2b99"
+-----------------------------+-------+
| Property | Value |
+-----------------------------+-------+
| cores | 20 |
| floating_ips | 10 |
| gigabytes | 1000 |
| injected_file_content_bytes | 10240 |
| injected_files | 5 |
| instances | 10 |
| metadata_items | 128 |
| ram | 51200 |
| volumes | 10 |
+-----------------------------+-------+
I also couldn't figure out how to get the quota-show to work as a member (non-admin) of a project.
Let me know if you want any of these issues broken out in to additional
bugs.
** Affects: nova
Importance: Medium
Assignee: Amandeep (rattenpal-amandeep)
Status: Confirmed
** Tags: security ux
--
quota-show should return error for invalid tenant id
https://bugs.launchpad.net/bugs/1031139
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).