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 protected]> 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 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1782309 Title: Confusing log message from scheduler Status in OpenStack Compute (nova): Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1782309/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
