yahoo-eng-team team mailing list archive

[OpenStack Infra <1960412@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/nova wallaby-eom  release.

** Changed in: nova/wallaby
       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/1960412

Title:
  Live migration artifacts are not cleaned up properly when queued live
  migration is aborted

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) wallaby series:
  Fix Released
Status in OpenStack Compute (nova) xena series:
  Fix Released

Bug description:
  Bug #1949808 describes one of the problems affecting aborted queued
  live migrations: VM's status is not reverted back to ACTIVE and VM is
  left in MIGRATING state.

  However that's not the single problem with aborted queued live
  migrations: some changes (port bindings on destination host, resource
  allocations and possibly instance's pci_requests) are introduced by
  Nova control plane before live migration actually started by source
  compute host. Those left-overs should also be removed.

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