cinder quota cannot be set by quota-update

Bug #1342524 reported by Yi Xuan Huang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

In my environment, I install cinder-api, cinder-scheduler on one controller node, and install cinder-volumes in another node. Using LVM driver.
The default value for cinder quota is 10 volumes, and 1000G limit.
When I create 10 * 1000G volumes, if I create another one, it will be prom opt message "ERROR: VolumeSizeExceedsAvailableQuota: CN-E34A1AA Requested volume or snapshot exceeds allowed Gigabytes quota. Requested 1G, quota is 1000G and 1000G has been consumed. (HTTP 413) (Request-ID: req-9fc0dd80-197d-48bc-82b4-567de7e196cc)
"
So I use 'cinder quota-update --volume=100 --gigabytes=1000000' to update quota information. But after that, when i try to create one more volume, it will be still prompt above message which said volumesizeexceedavailablequota.

I also changed /etc/cinder/cinder.conf to 100 and 1000000 as well. And restart all relate service(api,scheduler, volume). But it seems no effective for my environment.

And one more thing, when I see quota usage, it show 0 for in_use field.
[root@controller-a01 ~]# cinder quota-usage Public
+-----------+--------+----------+--------+
| Type | In_use | Reserved | Limit |
+-----------+--------+----------+--------+
| gigabytes | 0 | 0 | 100000 |
| snapshots | 0 | 0 | 45 |
| volumes | 0 | 0 | 100 |
+-----------+--------+----------+--------+

That make me very confuse.

At last, I use 'cinder quota-class-update' to update default quota, then I can create more volumes.

Is it a bug?

Revision history for this message
git-harry (git-harry) wrote :

If I remember correctly, cinderclient doesn't resolve the tenant name to a UUID for quota operations. If you have updated the quotas using 'Public' as the tenant ID that is likely the issue. When you check usage you are seeing nothing being used because the volumes are tracked by the UUID in cinder and not the tenant name.

Revision history for this message
Thang Pham (thang-pham) wrote :

There is a blueprint to validate tenant and user IDs that is pending: https://blueprints.launchpad.net/nova/+spec/validate-tenant-user-with-keystone. I plan to make a similar propose in cinder, once nova gets approved, because it would be similar code. It should resolve this bug and well as many other identical bugs.

Revision history for this message
John Griffith (john-griffith) wrote :

@git-harry is correct, we don't translate the name-->id. The cmd doesn't fail though so it's a bit confusing. We should probably return an error message if an ID isn't passed in here to help eliminate some of the confusion.

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.