nova quota not in sync with cinder quota

Bug #1078906 reported by Attila Fazekas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Low
Unassigned

Bug Description

I am using the volume_api_class = nova.volume.cinder.API in the nova.conf

tenant_id = 316a82031dde46418ab2551886db1afc (demo)

# nova quota-show 316a82031dde46418ab2551886db1afc
+-----------------------------+-------+
| 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 | 20 |
+-----------------------------+-------+

# cinder quota-show 316a82031dde46418ab2551886db1afc
+-----------+-------+
| Property | Value |
+-----------+-------+
| gigabytes | 1000 |
| volumes | 10 |
+-----------+-------+

# nova quota-update 316a82031dde46418ab2551886db1afc --volumes 42

# nova quota-show 316a82031dde46418ab2551886db1afc
+-----------------------------+-------+
| 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 | 42 |
+-----------------------------+-------+

# cinder quota-show 316a82031dde46418ab2551886db1afc
+-----------+-------+
| Property | Value |
+-----------+-------+
| gigabytes | 1000 |
| volumes | 10 |
+-----------+-------+

Both the cinder and the nova does not verify is the tenant-exists or at least looks like a tenant-id.
(I tried with tenant names too. )

Test version:
openstack-nova-volume-2012.2-1.fc18
openstack-cinder-2012.2-1.fc18

Revision history for this message
James King (jking-6) wrote :

The nova quota-update command doesn't update the value for volumes. The cinder command does work as advertised. The nova quota-show command does not appear to retrieve its value from cinder.

Changed in nova:
assignee: nobody → James King (jking-6)
status: New → In Progress
Revision history for this message
Joe Gordon (jogo) wrote :

the nova gigabytes and volumes quota have been removed: https://review.openstack.org/#/c/15602/

Revision history for this message
James King (jking-6) wrote :

looks like the "volumes" field wasn't removed from novaclient.

Revision history for this message
James King (jking-6) wrote :

See: https://bugs.launchpad.net/python-novaclient/+bug/1078089

novaclient has to support multiple versions, so the volume field is there

Changed in nova:
status: In Progress → Invalid
assignee: James King (jking-6) → nobody
Revision history for this message
Nikola Đipanov (ndipanov) wrote :

This is true, however, the output could be a bit more informative as Vish suggested in the proposed fix.

Changed in nova:
status: Invalid → In Progress
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
status: In Progress → Confirmed
Revision history for this message
Joe Gordon (jogo) wrote :

nova has removed the volumes API

Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.