yahoo-eng-team team mailing list archive

[fupingxie <1793644@xxxxxxxxxxxxxxxxxx>]

@Matt Riedemann sorry, I met this in newton, not on master.

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

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

Title:
  If an instance with anti-affinity was cold migrated, then it can not
  be selected to original host when migrate again.

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
     ===========
     If an instance with anti-affinity was cold migrated,
     then it can not be selected to original host.

     Steps to reproduce
     ==================
     0. I have two hypervisor node: node-1 and node-2
     1. create an Instance VM-1 with anti-affinity, it is allocated on node-1;
     2. cold migrate VM-1, then VM-1 was migrated to node-2;
     3. cold migrate VM-1 again.

     Expected result
     ===============
     The VM-1 will be migrated to node-1.

     Actual result
     =============
     Migration faild for “No valid host was found”.

     Environment
     ===========
     1. Two hypervisor nodes;

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