yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: compute-hyperv
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
     Assignee: Lucian Petrut (petrutlucian94)
         Status: In Progress


** Tags: hyper-v

** Also affects: nova
   Importance: Undecided
       Status: New

** Tags added: hyper-v

-- 
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

Status in compute-hyperv:
  New
Status in OpenStack Compute (nova):
  In Progress

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