yahoo-eng-team team mailing list archive

[tangxing <tang.xing@xxxxxxxxxx>]

Hi,sylvain-bauza, in some cases instance will be set to ERROR state when
migrate failed (such as UnableToMigrateToSelf),we can simply return the
error to upper layer (operater or user) to avoid make user run reset to
restore instance status since no changes to guest at all.

** Changed in: nova
       Status: Invalid => Confirmed

** Changed in: nova
   Importance: Wishlist => Low

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

Title:
  Cold migration fails when the filter only returns the host where the
  vm is located and the vm status is set to ERROR

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Description
  ===========
  The configuration: allow_resize_to_same_host=True.
  Cold migration fails when the filter only returns the host where the vm is located and the vm status is set to ERROR.

  Steps to reproduce
  ==================
  1、create a vm
  2、disable all hosts except the host which the vm is located
  3、cold migrate the vm, you can see the exception.UnableToMigrateToSelf in compute log, and the vm status is set to ERROR while it still running

  Expected result
  ===============
  cold migrate failed, and user should see HTTP400 NovaildHost from console output, because cold migrate to same host is meaningless. The vm status still keep Active.

  Actual result
  =============
  cold migrate failed, nothing returns from console, and vm status is set to ERROR.

  Environment
  ===========
  nova16.0.4   KVM $ libvirt

  Logs & Configs
  ==============
  allow_resize_to_same_host=True

  
  PS:
  If the host which the vm located is particularly resource-rich, filters return this host each time when user executes cold migration. Even if the resources of other hosts can meet the requirements of the virtual machine, the vm can never be cold-migrated.

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