yahoo-eng-team team mailing list archive

[Radoslav Gerganov <rgerganov@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Low
     Assignee: Radoslav Gerganov (rgerganov)
         Status: New

** Changed in: nova
   Importance: Undecided => Low

** Changed in: nova
     Assignee: (unassigned) => Radoslav Gerganov (rgerganov)

-- 
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):
  New

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