placement API allocation handling does not check min_unit, max_unit, step_size
Bug #1623545 reported by
Chris Dent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chris Dent |
Bug Description
The min_unit, max_unit and step_size values of resource provider inventory are not checked when submitting allocations. Only available capacity.
This is a known issue, a deliberate decision was made to put it off until later, but we need to record the presence of the issue. What's suppose to happen is that in addition to checking capacity, we also want to make sure that the allocation is between min_unit and max_unit and cleanly divisible by step_size. These checks should happen in the OVO code, not the API level.
Changed in nova: | |
assignee: | nobody → Ukesh (ukeshkumar) |
To post a comment you must log in.
By OVO code I'm assuming you mean the check should happen somewhere down in here:
https:/ /github. com/openstack/ nova/blob/ c651572d5acd883 8b1c1c0be1eeee1 1414205c57/ nova/objects/ resource_ provider. py#L810