Scheduler sends VM to HV that lacks resources
Albert.Braden at synopsys.com
Tue Nov 12 20:47:38 UTC 2019
We are running placement under apache:
The placement error logs show a lot of GETs but no errors:
We are planning to use NUMA but haven't started yet. It's probably a config error. Where should I be looking? This is our nova config on the controllers:
From: Sean Mooney <smooney at redhat.com>
Sent: Tuesday, November 12, 2019 12:22 PM
To: Albert Braden <albertb at synopsys.com>; openstack-discuss at lists.openstack.org
Subject: Re: Scheduler sends VM to HV that lacks resources
On Tue, 2019-11-12 at 19:42 +0000, Albert Braden wrote:
> If I create 20 VMs at once, at least one of them fails with "Exceeded maximum number of retries." When I look at the
> logs I see that the scheduler sent the VM to a host that doesn't have enough CPU "Free vcpu 14.00 VCPU < requested 16
> I thought that this must be caused by a race condition, so I stopped the scheduler and conductor on 2 controllers, and
> then created 20 more VMs. Now I see the logs only on controller 3, and some of the failures are now saying "Unable to
> establish connection to <LB>" but I still see the single scheduler sending VMs to a host that lacks resources "Free
> vcpu 14.00 VCPU < requested 16 VCPU."
> I'm looking at my nova.conf but don't see anything misconfigured. My filters are pretty standard:
> enabled_filters =
> What should I be looking for here? Why would a single scheduler send a VM to a host that is too full? We have lots of
> compute hosts that are not full:
> This is the command line I used:
> openstack server create --flavor s1.16cx120g --image QSC-P-CentOS6.6-19P1-v4 --network vg-network --max 20 alberttestB
what version of openstack are you running?
if its not using placement then this behaviour is expected as the resources are not claimed untill the vm is booted on
the node so there is and interval where the scudler is selecting hosts where you can race with other vm boot.
if you are using placement and you are not using numa or pci pass though, which you do not appear to be based on your
enabled filters, then this should not happen and we should dig deeper as there is likely a bug either in your
configuration or in nova.
More information about the openstack-discuss