OpenStack Compute (nova)

Lack of allocation candidates is only logged in DEBUG

Series queens
Bug #1794811

Bug #1794811 reported by Mohammed Naser on 2018-09-27

This bug affects 1 person

	Status	Importance	Assigned to
OpenStack Compute (nova)	Fix Released	Medium	Mohammed Naser
Pike	Confirmed	Medium	Unassigned
Queens	Confirmed	Medium	Unassigned
Rocky	Fix Committed	Medium	Mohammed Naser

Bug Description

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

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-09-27: Fix proposed to nova (master)

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

Changed in nova:
assignee:	nobody → Mohammed Naser (mnaser)
status:	New → In Progress

Matt Riedemann (mriedem) on 2018-09-27

Changed in nova:
importance:	Undecided → Medium

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-09-27: Fix proposed to nova (stable/rocky)

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

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-09-30: Fix merged to nova (master)

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

Changed in nova:
status:	In Progress → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-10-01: Fix merged to nova (stable/rocky)

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.

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