cpu binding conflict when multiple VMs execute unshelve at the same time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
Undecided
|
tangxing |
Bug Description
Description
===========
hw:cpu_policy of flavor is dedicated,use this flavor create six vms.Then excute 'nova shelve <server-id' command,after vm's state become to SHELVE_
the same time.This will lead to server vms bind to same cpu.
Steps to reproduce
==================
1:nova flavor-key 1 set hw:cpu_
2:[root@nail-5300-1 ~(keystone_admin)]# nova boot --flavor 1 --image 22164f51-
3:nova shelve test-1
nova shelve test-2
nova shelve test-3
nova shelve test-4
nova shelve test-5
nova shelve test-6
4:
nova unshelve test-1
nova unshelve test-2
nova unshelve test-3
nova unshelve test-4
nova unshelve test-5
nova unshelve test-6
Actual result
=============
[root@E9000slot6 /]# virsh vcpupin 24
VCPU: CPU Affinity
-------
0: 9
1: 33
[root@E9000slot6 /]# virsh vcpupin 25
VCPU: CPU Affinity
-------
0: 9
1: 33
Logs & Configs
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
2017-12-21 19:12:46.417 23081 ERROR nova.compute.
Changed in nova: | |
assignee: | nobody → tangxing (tang-xing) |
That's a known issue that needs some design discussions in order to fix it correctly. The main upstream bug is https:/ /bugs.launchpad .net/nova/ +bug/1417667 for all the move ops.