Confusing log message from scheduler

[Radoslav Gerganov]

If there are not enough resources for spawning an instance, we get this message in the scheduler log:

"""
Got no allocation candidates from the Placement API. This may be a temporary occurrence as compute nodes start up and begin reporting inventory to the Placement service.
"""

Not having enough resources for creating the instance is a lot more probable reason for no allocation candidates than compute node is just starting up. I think the log message should state both reasons, not having enough resources being first.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/583486

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/583486
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3fe54a74d8a3b5d5338a902e3562733a2b9a564
Submitter: Zuul
Branch: master

commit c3fe54a74d8a3b5d5338a902e3562733a2b9a564
Author: Radoslav Gerganov <email address hidden>
Date: Wed Jul 18 11:02:00 2018 +0300

    Fix confusing log message in scheduler

    Not having enough resources for creating the instance is a lot more
    probable reason for no allocation candidates than compute node is just
    starting up. This patch changes the log message to state both reasons.

    Change-Id: I5d0cefbf833e797d560e115148beae35b0c48959
    Closes-Bug: #1782309

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.