nova blocks vdpa move operations that work correctly.
Bug #1970467 reported by
sean mooney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
sean mooney | ||
Wallaby |
In Progress
|
Medium
|
sean mooney | ||
Xena |
Fix Released
|
Medium
|
sean mooney | ||
Yoga |
Fix Released
|
Medium
|
sean mooney | ||
Zed |
Fix Released
|
Medium
|
sean mooney |
Bug Description
during the implementation of the initall VDPA feature support i only had one server with vdpa capable nics.
as a result no move operations were actually tested so we choose out of an abundance of cation
to block them at the API level until we had a chance to test them.
They have now been tested and work without code change once the API block is removed
during the zed ptg we agreed to treat this as a bug and remove the API block.
once this is complete cold migration, resize, evacuate and shelve/unshelve will be available when using interfaces with vnic-type vdpa.
Changed in nova: | |
status: | Triaged → In Progress |
To post a comment you must log in.
setting to medium as supporting move operations like evacuate and cold migrate is essitaly for most operators to reasonably deploy vdpa but for those that did not require that its just a nice to have that simlifys day too operations.
so medium feels about right as those that don't use vdpa are not impacted and does that doo presumable knew the limitations when the decided to deploy it.