Create volume failed due to quota exceeded in spite of quota number updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Ian Govett |
Bug Description
Defect log:
-------
File "/usr/lib/
self.setUp()
File "/usr/lib/
self.
File "/usr/lib/
try_
File "/usr/lib/
return func()
File "/opt/stack/
cls.volume = cls.create_volume()
File "/opt/stack/
**kwargs)
File "/opt/stack/
resp, body = self.post(
File "/opt/stack/
return self.request(
File "/opt/stack/
resp, resp_body)
File "/opt/stack/
raise exceptions.
OverLimit: Quota exceeded
Details: {'message': 'VolumeLimitExc
-------
Create volume using tenant: admin
[root@localhost]# keystone tenant-list
+------
| id | name | enabled |
+------
| 54ce53cb1ed3422
Tried configure 3 ways as following but all failed:
-------
In /etc/cinder/
quota_volumes = 100
[NG] restart cinder-api doesn't work.
-------
>> cinder quota-update --volumes 100 admin
[NG] restart cinder-api doesn't work.
-------
>> Tried modify the code of "/opt/stack/
quota_opts = [
cfg.
cfg.
cfg.
[NG] restart cinder-api doesn't work.
-------
Finally I found a workaround is:
>> cinder quota-update --volumes 100 54ce53cb1ed3422
Update the quota using project_id instead of project_name, it does work.
I believe this is a bug in "/opt/stack/
def limit_check()
....
project_id = context.project_id
....
and "/opt/stack/
I hope someone who has more insight(who refactor the create volume task flow) could check how this defect got addressed.
Changed in cinder: | |
assignee: | nobody → Juan Manuel Ollé (juan-m-olle) |
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
assignee: | nobody → Ian Govett (igovett) |
Hi Jerry,
Here is the link page introducing how the quota is changed for cinder http:// docs.openstack. org/user- guide-admin/ content/ cli_set_ quotas. html. And it is cerntain that the second way you are trying "cinder quota-update --volumes 100 admin" is not working, cos you need to specify the tenant id instead of tenant name.
I think this is not a bug, but a new workround maybe. If we change the quota in the conf file, then we change the quota after a successful restart. However, I am a bit concerned about it, because we may need a lot of validation. Fow example, if we reduce the quota to 20 volumes, and we have already had 21volumes. How shall we deal with this situation? A sucessful restart with warning? with error? or with ....? It gets a bit sticky.