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. :-) > > By the way, I am using the Queens release. > > Regards,
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
