quota settings are ignored by nova

[Botho Hohbaum]

nova ignores custom quota settings. quota had been changed for the admin tenant, but it seems, that still the default values are active. these are my settings:

root@clc ~ # nova quota-show admin
Please enter password for encrypted keyring:
+-----------------------------+-------+
| Property | Value |
+-----------------------------+-------+
| cores | 32 |
| floating_ips | 12 |
| gigabytes | 1000 |
| injected_file_content_bytes | 10240 |
| injected_files | 5 |
| instances | 16 |
| metadata_items | 128 |
| ram | 51200 |
| volumes | 16 |
+-----------------------------+-------+
root@clc ~ # nova quota-defaults admin
Please enter password for encrypted keyring:
+-----------------------------+-------+
| 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 |
+-----------------------------+-------+
root@clc ~ # nova boot --image da322596-2a3a-44c6-8d72-cd82bf1da82a --flavor 1 --key_name my-private-key --security_groups default test-vm
Please enter password for encrypted keyring:
ERROR: Quota exceeded for instances: Requested 1, but already used 10 of 10 instances (HTTP 413) (Request-ID: req-867b3a5a-c17b-4c6c-b098-2a83a3be8e5d)

the installation consists of six nodes, 2x swift storage, 1x nova-volume, 2x compute nodes - and one "cloud controller" for the rest. no nova-network, quantum instead. moosefs is used on the compute nodes for live-migration.

please let me know, what further information you need to find the roots of this issue.

[differentlocal (differentlocal)]

Affected me too.

Root of this behavior is in differences between tenant NAME and tenant ID.

If I have tenant 'admin' with ID '6eb505f5d85142a0a7c01686ef0f5a6e', nova quota-show <name> and nova quota-show <ID> returns different results - real values for ID and default values for name.

And (and this is really bad) quota-show doesn't say us, what (name or ID) it using now and no error returns (even if no tenant with given name and/or ID exists in keystone). Nova silently showing default quota.

I think, correct behavior is:

- If argument is name - lookup keystone for ID and show quota by ID.
- If given name not found - return error.
- If argument is ID - show quota for this ID
- If given ID not found - return error too.

[Amandeep (rattenpal-amandeep)]

@Abhishek Lahiri - I want to work on this bug, please let me know if you are not working on it.

[Neetu Jain (nutshi)]

Aman and Abhishek .. I am assuming you are not working on it

[Neetu Jain (nutshi)]

any pointers on how to add tenant-name to tenant-Id lookup in novaclient/v2/shell.py