yahoo-eng-team team mailing list archive

[OpenStack Infra <1841411@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/678480
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=a721681e6111d85264e20085d1f184d1c923b69e
Submitter: Zuul
Branch:    master

commit a721681e6111d85264e20085d1f184d1c923b69e
Author: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Mon Aug 26 10:28:37 2019 +0300

    Avoid error state for recovered instances after failed migrations
    
    Most users expect that if a live migration fails but the instance
    is fully recovered, it shouldn't enter 'error' state. Setting
    the migration status to 'error' should be enough. This simplifies
    debugging, making it clear that the instance dosn't have to be
    manually recovered.
    
    This patch changed this behavior, indirectly affecting the Hyper-V
    driver: Idfdce9e7dd8106af01db0358ada15737cb846395
    
    We'll stop propagating exceptions when managing to recover the
    instance, which matches the reference driver (libvirt) behavior.
    
    Change-Id: I4b667c06e008b03457d35ce9c920b916d21c255f
    Closes-Bug: 1841411


** Changed in: compute-hyperv
       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/1841411

Title:
  Instances recovered after failed migrations enter error state
  (hyper-v)

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  New
Status in OpenStack Compute (nova) rocky series:
  New
Status in OpenStack Compute (nova) stein series:
  New

Bug description:
  Most users expect that if a live migration fails but the instance is
  fully recovered, it shouldn't enter 'error' state. Setting the
  migration status to 'error' should be enough. This simplifies
  debugging, making it clear that the instance dosn't have to be
  manually recovered.

  This patch changed this behavior, indirectly affecting the Hyper-V
  driver, which propagates migration errors:
  Idfdce9e7dd8106af01db0358ada15737cb846395

  When using the Hyper-V driver, instances enter error state even after
  successful recoveries. We may copy the Libvirt driver behavior and
  avoid propagating exceptions in this case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1841411/+subscriptions