KeyError when booting multi-stagger-instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned |
Bug Description
Description
===========
Bulk boot multi instances in a short time, if the amount of resources required is not the same,
and the number of resources owned by the compute node is also different, there maybe a KeyError
in nova-scheduler.log .
Steps to reproduce
==================
For example, I have four compute nodes:
host1-3, with 24 cpus and 120G ram
host4, with 12 cpus and 40G ram
And i will boot 12 instances at the same time in different cmd,
one of them need 16 cpus and 48G ram, others need 1 cpus and 1G ram.
Then the fault appeared, some of instances ERROR.
Expected result
===============
all instance boot success.
Actual result
=============
some instances ERROR.
Environment
===========
OpenStack version:
Queens
Hypervisor:
Libvirt + KVM
Storage:
LVM
Networking:
Neutron with OpenVSwitch
Logs & Configs
==============
In nova-scheduler.log
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
2018-12-10 15:05:15.029 26837 ERROR oslo_messaging.
Are you able to reproduce with debug logging enabled and then provide (attach) the full scheduler log so that we can get the details about which filters and such are used?