yahoo-eng-team team mailing list archive

[OpenStack Infra <1960412@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/nova/+/828570
Committed: https://opendev.org/openstack/nova/commit/219520d9cec6a204e0d0f75881d75c8db48e7f56
Submitter: "Zuul (22348)"
Branch:    master

commit 219520d9cec6a204e0d0f75881d75c8db48e7f56
Author: Alexey Stupnikov <aleksey.stupnikov@xxxxxxxxx>
Date:   Mon Mar 7 16:57:39 2022 +0100

    Clean up when queued live migration aborted
    
    This patch solves bug #1949808 and bug #1960412 by tuning
    live_migration_abort() function and adding calls to:
    
    - remove placement allocations for live migration;
    - remove INACTIVE port bindings against destination compute node;
    - restore instance's state.
    
    Related unit test was adjusted and related functional tests were
    fixed.
    
    Closes-bug: #1949808
    Closes-bug: #1960412
    
    Change-Id: Ic97eff86f580bff67b1f02c8eeb60c4cf4181e6a


** Changed in: nova
       Status: In Progress => 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

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