Open Stack

On 08/08/2018 09:37 AM, Cody wrote:
>> On 08/08/2018 07:19 AM, Bernd Bausch wrote:
>>> I would think you don't even reach the scheduling stage. Why bother
>>> looking for a suitable compute node if you exceeded your quota anyway?
>>>
>>> The message is in the conductor log because it's the conductor that does
>>> most of the work. The others are just slackers (like nova-api) or wait
>>> for instructions from the conductor.
>>>
>>> The above is my guess, of course, but IMHO a very educated one.
>>>
>>> Bernd.
> 
> Thank you, Bernd. I didn't know the inner workflow in this case.
> Initially, I thought it was for the scheduler to discover that no more
> resource was left available, hence I expected to see something from
> the scheduler log. My understanding now is that the quota get checked
> in the database prior to the deployment. That would explain why the
> clue was in the nova-conductor.log, not the nova-scheduler.log.

Quota is checked in the nova-api node, not the nova-conductor.

As I said in my previous message, unless you paste what the logs are 
that you are referring to, it's not possible to know what you are 
referring to.

Best,
-jay