nova-manage project quota command confusing with keystone
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
The "nova-manage project quota" command, when used with keystone based authentication, requires that you use project id (tenant id) for the parameter currently displayed as <Project name>. If you use the tenant name, it does not give an error and even seems to work. For example:
# nova-manage project quota admin
metadata_items: 128
instances: 10
injected_
injected_files: 5
volumes: 10
gigabytes: 1000
cores: 20
ram: 51200
floating_ips: 10
# nova-manage project quota --help
Usage: nova-manage project quota <args> [options]
Options:
-h, --help show this help message and exit
--project=
--key=<key> Key
--value=<value> Value
# nova-manage project quota --project=admin --key=volumes --value=40
metadata_items: 128
instances: 10
injected_
injected_files: 5
volumes: 40
gigabytes: 1000
cores: 20
ram: 51200
floating_ips: 10
#
If you attempt to add more than 10 volumes, however, it will fail because the quota actually imposed is the one used for the tenant id, not the tenant name.
There are several other places, apparently, in the nova-manage code which are similar and may have similar problems.
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Dean Troyer (dtroyer) wrote | #1 |
| tags: | added: docimpact |
| James Kyle (jkyle) wrote | #2 |
| li,chen (chen-li) wrote | #3 |
This is due to the nature of nova-manage, which is primarily a database editor for nova and does not include client capability for other services, ie keystone. I believe the long-term plan is to replace nova-manage with tools using the admin api.