min_count ignored for instance create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mike BRIGHT | ||
Havana |
Fix Released
|
Medium
|
Nikola Đipanov |
Bug Description
The server create API takes min_count and max_count values for the number of instances to be created, where the actual number to be created should be the highest value allowed by quota between these limits.
However the code in compute/api.py does a single check against max_count and then treats the exeception as a failure - resulting in messages such as:
min_count=1
max_count= (quota+1)
"Quota exceeded for instances: Requested 1, but already used 13 of 40 instances"
The code in _check_
Changed in nova: | |
assignee: | nobody → Mike BRIGHT (k5-openstack) |
tags: | added: api |
Changed in nova: | |
status: | Incomplete → Confirmed |
tags: | added: quotas |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → icehouse-1 |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
Did you see this problem with Havana? Do you have a testcase?
It looks like _check_ num_instances_ quota does adjust the number of instances if the quota reserveration fails and then recursively call itself with the lower number.