[Nova] Evacuation doesn't respect anti-affinity rules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
High
|
Oleksiy Molchanov | ||
9.x |
Won't Fix
|
High
|
Oleksiy Molchanov | ||
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Balazs Gibizer |
Bug Description
--- Environment ---
MOS: 9.2
Nova: 13.1.1-
3 compute nodes
--- Steps to reproduce ---
1. Create a new server group:
nova server-group-create anti anti-affinity
2. Launch 2 VMs in this server group:
nova boot --image TestVM --flavor m1.tiny --nic net-id=
nova boot --image TestVM --flavor m1.tiny --nic net-id=
3. Stop nova-compute on the nodes where these 2 VMs are running:
nova show vm-1 | grep "hypervisor"
OS-EXT-
nova show vm-2 | grep "hypervisor"
OS-EXT-
[root@node-12 ~]$ service nova-compute stop
nova-compute stop/waiting
[root@node-13 ~]$ service nova-compute stop
nova-compute stop/waiting
4. Evacuate both VMs almost at once:
nova evacuate vm-1
nova evacuate vm-2
5. Check where these 2 VMs are running:
nova show vm-1 | grep "hypervisor"
nova show vm-2 | grep "hypervisor"
--- Actual behavior ---
Both VMs have been evacuated on the same node:
[root@node-11 ~]$ virsh list
Id Name State
-------
2 instance-00000001 running
3 instance-00000002 running
--- Expected behavior ---
According to the anti-affinity rule, only 1 VM is evacuated.
Another one failed to evacuate with the appropriate message.
Changed in mos: | |
assignee: | nobody → Oleksiy Molchanov (omolchanov) |
Changed in mos: | |
status: | New → Won't Fix |
sla1 for 9.0-updates