Open Stack

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.
> 
> On 8/8/2018 1:35 AM, Cody wrote:
>> Hi Jay,
>>
>> Thank you for getting back to my question.
>>
>> I agree that it is not an error; only a preset limit is reached. I
>> just wonder why this incident only got recorded in the
>> nova-conductor.log, but not in other files such as nova-scheduler.log,
>> which would make more sense to me. :-)

I gave up trying to answer this because the original poster did not 
include any information about an "error" in either the original post [1] 
or his reply.

So I have no idea what got recorded in the nova-conductor log at all.

Until I get some details I have no idea how to further answer the 
question (or even if there *is* a question still?).

[1] http://lists.openstack.org/pipermail/openstack/2018-August/046804.html

>> By the way, I am using the Queens release.
>>
>> Regards,
> 
> 
> 
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>