Nova does not respect ram quotas
Bug #828416 reported by
Jake Dahn
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Currently if you set a ram quota (the default value is 51200) for a tenant, and launch multiple instances which exceed this quota they will not error out.
Nova should respect these quotas.
| Changed in nova: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Sateesh (sateesh-chodapuneedi) wrote | #1 |
| Changed in nova: | |
| status: | Confirmed → Fix Committed |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Jan,
I have tested ram quotas with diablo release and found it working.
Are you seeing this issue still?
If you are setting the quota using dashboard UI, then the ram limit you set will be multiplied by 100. So if you see 512 in dashboard UI as quota that means 51200 is actual limit as per nova. It's a dashboard issue. I have set the quota using nova-manage and found nova validating the limits/quotas correctly.
Regards,
Sateesh