yahoo-eng-team team mailing list archive

[Boxiang Zhu <zhu.boxiang@xxxxxxxxxxx>]

Public bug reported:

Description
===========
If we live migrate two instance simultaneously, the instances will break the instance group policy.

Steps to reproduce
==================
OpenStack env with three compute nodes(node1, node2 and node3). Then we create two VMs(vm1, vm2) with the anti-affinity policy.
At last, we live migrate two VMs simultaneously.

Before live-migration, the VMs are located as followed:
node1  ->  vm1
node2  ->  vm2
node3

* nova live-migration vm1
* nova live-migration vm2

Expected result
===============
Fail to live migrate vm1 and vm2.

Actual result
=============
node1
node2
node3  ->  vm1,vm2

Environment
===========
master branch of openstack

As described above, the live migration could not check the in-progress
live-migration and just select the host by scheduler filter. So that
they are migrated to the same host.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  Description
  ===========
  If we live migrate two instance simultaneously, the instances will break the instance group policy.
  
- 
  Steps to reproduce
  ==================
- OpenStack env with three compute nodes(node1, node2 and node3). Then we create two VMs(vm1, vm2) 
- with the anti-affinity policy.
+ OpenStack env with three compute nodes(node1, node2 and node3). Then we create two VMs(vm1, vm2) with the anti-affinity policy.
  At last, we live migrate two VMs simultaneously.
  
  Before live-migration, the VMs are located as followed:
  node1  ->  vm1
  node2  ->  vm2
  node3
  
  * nova live-migration vm1
  * nova live-migration vm2
  
- 
  Expected result
  ===============
  Fail to live migrate vm1 and vm2.
- 
  
  Actual result
  =============
  node1
  node2
  node3  ->  vm1,vm2
  
- 
  Environment
  ===========
  master branch of openstack
  
- 
- As described above, the live migration could not check the in-progress live-migration and just select the host by scheduler filter. So that they are migrated to the same host.
+ As described above, the live migration could not check the in-progress
+ live-migration and just select the host by scheduler filter. So that
+ they are migrated to the same host.

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

Title:
  live migration break the anti-affinity policy of server group
  simultaneously

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  If we live migrate two instance simultaneously, the instances will break the instance group policy.

  Steps to reproduce
  ==================
  OpenStack env with three compute nodes(node1, node2 and node3). Then we create two VMs(vm1, vm2) with the anti-affinity policy.
  At last, we live migrate two VMs simultaneously.

  Before live-migration, the VMs are located as followed:
  node1  ->  vm1
  node2  ->  vm2
  node3

  * nova live-migration vm1
  * nova live-migration vm2

  Expected result
  ===============
  Fail to live migrate vm1 and vm2.

  Actual result
  =============
  node1
  node2
  node3  ->  vm1,vm2

  Environment
  ===========
  master branch of openstack

  As described above, the live migration could not check the in-progress
  live-migration and just select the host by scheduler filter. So that
  they are migrated to the same host.

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