yahoo-eng-team team mailing list archive

[Balazs Gibizer <balazs.gibizer@xxxxxxxx>]

Public bug reported:

Steps to reproduce
==================
1) boot a server with --availability-zone <az>:<host> This will force nova to boot the server on the given host
2) Try to migrate the server in a situation when the first destination host of the migration selected by the scheduler will fail (e.g. move_claim fails) but there are alternate hosts that could support the migration.

Expected result
===============

Migration is re-scheduled after the first failure and can succeed on an
alternate destination.

Actual result
=============
Nova does not try to re-schedule the migration after the first failure. Server goes to ERROR state.

** Affects: nova
     Importance: Undecided
     Assignee: Balazs Gibizer (balazs-gibizer)
         Status: New


** Tags: migration reschedule

** Tags added: migration reschdule

** Tags removed: reschdule
** Tags added: reschedule

** Changed in: nova
     Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

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

Title:
  migration is not recheduled if the server originally booted with
  --availability-zone <az>:<host>

Status in OpenStack Compute (nova):
  New

Bug description:
  Steps to reproduce
  ==================
  1) boot a server with --availability-zone <az>:<host> This will force nova to boot the server on the given host
  2) Try to migrate the server in a situation when the first destination host of the migration selected by the scheduler will fail (e.g. move_claim fails) but there are alternate hosts that could support the migration.

  Expected result
  ===============

  Migration is re-scheduled after the first failure and can succeed on
  an alternate destination.

  Actual result
  =============
  Nova does not try to re-schedule the migration after the first failure. Server goes to ERROR state.

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