Limit -1 in trove quota-show does not means unlimited like other projects
Bug #1729791 reported by
Fan Zhang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Fan Zhang |
Bug Description
When I met "QuotaExceeded: Quota exceeded for resources: ['volumes']" earlier this day, I tried to update trove quota with limit -1, as I did in other projects like nova, cinder etc. But it couldn't solve the problem. So I went to the code [1] and found out that -1 in trove quota-show did not means unlimited.
In my opinion, I do think we should support -1 as unlimited resource in trove.
Secondly, I found out that when we update quota, the check for limit could be extended to
accept only -1, not -2 or other negative numbers.
It would be more appropriate to call this bug as a functional supplement
description: | updated |
Changed in trove: | |
assignee: | nobody → Fan Zhang (fanzhang) |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/517569
Review: https:/