Quotas functionality seems broken in Nova
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Vish Ishaya |
Bug Description
I checked out the latest Nova code
(Commit: https:/
Steps:
1. Login to Dashboard as an admin and set quota limits for your project.
2. Try creating instances for that project greater than the set quota limits.
Expected: Quota exceeded messages after an attempt to create instance once the quota limit is reached
Actual: Instances greater than the allowed quota were created
I checked the database entries after performing the above steps. The instances and cores usages were above the hard limits.
http://
This was reproducible for any quota resource (instances, cores, ram etc.)
Besides checking this manually, the Tempest Whitebox tests that test the quota functionality also captured these failures:
description: | updated |
Changed in nova: | |
importance: | Undecided → High |
milestone: | none → folsom-3 |
status: | New → Confirmed |
Changed in nova: | |
importance: | High → Critical |
Changed in nova: | |
assignee: | Eoghan Glynn (eglynn) → Vish Ishaya (vishvananda) |
Changed in nova: | |
milestone: | folsom-3 → 2012.2 |
This is a recent regression. See comment #1 in https:/ /bugs.launchpad .net/tempest/ +bug/1034129