yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74813
[Bug 1793644] [NEW] If an instance with anti-affinity was cold migrated, then it can not be selected to original host when migrate again.
Public bug reported:
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;
** Affects: nova
Importance: Undecided
Assignee: fupingxie (fpxie)
Status: New
** Summary changed:
- If an instance with anti-affinity was cold migrated, then it can not be selected to original host.
+ If an instance with anti-affinity was cold migrated, then it can not be selected to original host when migrate again.
** Changed in: nova
Assignee: (unassigned) => fupingxie (fpxie)
--
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):
New
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
Follow ups