yahoo-eng-team team mailing list archive

[Boxiang Zhu <zhu.boxiang@xxxxxxxxxxx>]

Public bug reported:

Description
===========
When we evacuate multi servers simultaneously, it will break the anti-affinity rules of group.

Environment
===========
Prepare three nodes and deploy the multi nodes cluster with kolla-ansible.

Steps to reproduce
==================
1. we have 3 compute nodes
2. we created a server group with anti-affinity policy
=> nova server-group-create anti anti-affinity
3. we create 2 servers with this server group
=> nova boot --image cirros --flavor m1.tiny --nic net-id=ae01e08e-98af-402f-b057-0481fd80a874 --hint group=16b0d654-4cdb-45dc-b2cf-cac68e30c79e vm01
=> nova boot --image cirros --flavor m1.tiny --nic net-id=ae01e08e-98af-402f-b057-0481fd80a874 --hint group=16b0d654-4cdb-45dc-b2cf-cac68e30c79e vm02
4. we stop nova-compute service on the nodes where 2 VMs are running
=> nova show vm01 | grep "hypervisor"
=> nova show vm02 | grep "hypervisor"
=> docker stop nova_compute[on two compute nodes]
5. we evacuate 2 VMs at once
=> nova evacuate vm01
=> nova evacuate vm02
6. we check where 2 VMs are running now
=> nova show vm01 | grep "hypervisor"
=> nova show vm02 | grep "hypervisor"

Expected result
===============
1. both of them failed to evacuate
2. one of them succeeded to evacuate to the last node, and another failed to evacuate

Actual result
=============
1. both of them succeeded to evacuate to the last node

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: evacuate

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

Title:
  Evacuation still doesn't respect anti-affinity rules after adding late
  group check

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  When we evacuate multi servers simultaneously, it will break the anti-affinity rules of group.

  Environment
  ===========
  Prepare three nodes and deploy the multi nodes cluster with kolla-ansible.

  Steps to reproduce
  ==================
  1. we have 3 compute nodes
  2. we created a server group with anti-affinity policy
  => nova server-group-create anti anti-affinity
  3. we create 2 servers with this server group
  => nova boot --image cirros --flavor m1.tiny --nic net-id=ae01e08e-98af-402f-b057-0481fd80a874 --hint group=16b0d654-4cdb-45dc-b2cf-cac68e30c79e vm01
  => nova boot --image cirros --flavor m1.tiny --nic net-id=ae01e08e-98af-402f-b057-0481fd80a874 --hint group=16b0d654-4cdb-45dc-b2cf-cac68e30c79e vm02
  4. we stop nova-compute service on the nodes where 2 VMs are running
  => nova show vm01 | grep "hypervisor"
  => nova show vm02 | grep "hypervisor"
  => docker stop nova_compute[on two compute nodes]
  5. we evacuate 2 VMs at once
  => nova evacuate vm01
  => nova evacuate vm02
  6. we check where 2 VMs are running now
  => nova show vm01 | grep "hypervisor"
  => nova show vm02 | grep "hypervisor"

  Expected result
  ===============
  1. both of them failed to evacuate
  2. one of them succeeded to evacuate to the last node, and another failed to evacuate

  Actual result
  =============
  1. both of them succeeded to evacuate to the last node

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