openstack
/
nova
Code Issues Proposed changes

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
This commit is contained in:
Mohammed Naser 2018-09-27 10:55:52 -04:00
parent e658f41d68
commit a520353652
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
nova/scheduler/manager.py
View File

@ -147,10 +147,10 @@ class SchedulerManager(manager.Manager):
(alloc_reqs, provider_summaries,
allocation_request_version) = res
if not alloc_reqs:
LOG.debug("Got no allocation candidates from the Placement "
"API. This could be due to insufficient resources "
"or a temporary occurrence as compute nodes start "
"up.")
LOG.info("Got no allocation candidates from the Placement "
"API. This could be due to insufficient resources "
"or a temporary occurrence as compute nodes start "
"up.")
raise exception.NoValidHost(reason="")
else:
# Build a dict of lists of allocation requests, keyed by