Lack of allocation candidates is only logged in DEBUG

[Mohammed Naser]

If the placement service gets allocation candidates, it goes through all the filters and if it ends up with 0 compute nodes, it logs it in INFO:

https://github.com/openstack/nova/blob/c6218428e9b29a2c52808ec7d27b4b21aadc0299/nova/filters.py#L130

However, if no allocation candidates match, it throw a message in DEBUG and exits out, leaving important information for the operator.

https://github.com/openstack/nova/blob/c3fe54a74d8a3b5d5338a902e3562733a2b9a564/nova/scheduler/manager.py#L150-L153

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605771

[OpenStack Infra (hudson-openstack)]

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

commit a5203536520578f016c6e0f849264039ff146f14
Author: Mohammed Naser <email address hidden>
Date: Thu Sep 27 10:55:52 2018 -0400

    Use INFO for logging no allocation candidates

    If the placement service returns no allocation candidates, the
    log message is done in DEBUG leaving no information for the
    operator to have visiblity on why the NoValidHost was raised.

    If we do get something from the placement service that results
    in 0 compute nodes after going through filters, we do log a
    message in INFO. This is to add consistency for a message
    in INFO if we have no allocation candidates.

    Closes-Bug: #1794811
    Change-Id: Ief2277b3a973dd2f947f354f844ce1c6c4d6026a

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605771
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18cc479316e872ecf320136e160bdee5eb3f7469
Submitter: Zuul
Branch: stable/rocky

commit 18cc479316e872ecf320136e160bdee5eb3f7469
Author: Mohammed Naser <email address hidden>
Date: Thu Sep 27 10:55:52 2018 -0400

    Use INFO for logging no allocation candidates

    If the placement service returns no allocation candidates, the
    log message is done in DEBUG leaving no information for the
    operator to have visiblity on why the NoValidHost was raised.

    If we do get something from the placement service that results
    in 0 compute nodes after going through filters, we do log a
    message in INFO. This is to add consistency for a message
    in INFO if we have no allocation candidates.

    Closes-Bug: #1794811
    Change-Id: Ief2277b3a973dd2f947f354f844ce1c6c4d6026a
    (cherry picked from commit a5203536520578f016c6e0f849264039ff146f14)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 18.0.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.