TooManyInstances msg is misleading if ram or cores over-quota
Bug #1031737 reported by
Eoghan Glynn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Eoghan Glynn | ||
Bug Description
The TooManyInstances exception message is misleading if it's the ram or cores resource that has gone over-quota, as opposed to the raw number of instances.
For example if only 6 instances are in use, against a quota of say 10, but then a request to start an xlarge fails because the required 16384Mb memory would cause the ram resource to go over-quota, then the exception message returned to the client would be:
'Quota exceeded for ram: Requested 1, but already used 6 of 6 instances'
whereas it would be more meaningful as, for example:
'Quota exceeded for ram: Requested 16384, but already used 90112 of 98304 ram'
| Changed in nova: | |
| assignee: | nobody → Eoghan Glynn (eglynn) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| importance: | Undecided → Low |
| milestone: | none → folsom-3 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | folsom-3 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/