yahoo-eng-team team mailing list archive

[OpenStack Infra <1970467@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/nova 24.2.0  release.

** Changed in: nova/xena
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1970467

Title:
  nova blocks vdpa move operations that work correctly.

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) wallaby series:
  In Progress
Status in OpenStack Compute (nova) xena series:
  Fix Released
Status in OpenStack Compute (nova) yoga series:
  Fix Released
Status in OpenStack Compute (nova) zed series:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1970467/+subscriptions