cinder quota cannot be set by quota-update
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: VolumeSizeExcee
"
So I use 'cinder quota-update --volume=100 --gigabytes=
I also changed /etc/cinder/
And one more thing, when I see quota usage, it show 0 for in_use field.
[root@controlle
+------
| 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?
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.