Quotas code should not raise exceptions when resources are being deleted
Bug #1178285 reported by
Nate Bensimon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Steve Leon | ||
Bug Description
Scenario:
1. Set quota for resource (instances or volume) below their current resource usage
2. Delete resource to bring the current usage down
Expected Behavior:
1. Resource is deleted and quota usage is updated accordingly
Actual Behavior:
1. Failure in deleting the resource due to quota check (raises the quota exceeded exception -- 413)
Revision history for this message
| Steve Leon (steve-leon) wrote | #1 |
| Changed in reddwarf: | |
| assignee: | nobody → Steve Leon (steve-leon) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to reddwarf (master) | #2 |
| Changed in reddwarf: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to trove (master) | #3 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| milestone: | none → havana-2 |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Hi Nate,
Thanks for this finding. This happens because the quota calculation runs at a resource gets reserved either for create, delete or update.
We'll look for a fix soon. But the workaround would be to set the quota to a value above the current resource usage and delete again.