Got it! Thank you, Jay! - Cody
On Wed, Aug 8, 2018 at 11:36 AM Jay Pipes wrote:
>
> So, that is normal operation, actually. The conductor calls the
> scheduler to find a place for your requested instances. The scheduler
> responded to the conductor that, sorry, there were no hosts that were
> abl
So, that is normal operation, actually. The conductor calls the
scheduler to find a place for your requested instances. The scheduler
responded to the conductor that, sorry, there were no hosts that were
able to match the request (I don't know what the details of that request
were).
And so th
Hi Jay,
Thank you for getting back. I attached the log in my previous reply,
but I guess Gmail hided it from you as a quoted message. Here comes
again:
From nova-conductor.log
### BEGIN ###
2018-08-08 09:28:35.974 1648 ERROR nova.conductor.manager
[req-ef0d8ea1-e801-483e-b913-9148a6ac5d90
2499343
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
mos
> 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
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 sl
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 instruction
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
On 08/07/2018 10:57 AM, Cody wrote:
Hi everyone,
I intentionally triggered an error by launching more instances than it
is allowed by the 'cpu_allocation_ratio' set on a compute node. When it
comes to logs, the only place contained a clue to explain the launch
failure was in the nova-conducto
Hi everyone,
I intentionally triggered an error by launching more instances than it is
allowed by the 'cpu_allocation_ratio' set on a compute node. When it comes
to logs, the only place contained a clue to explain the launch failure was
in the nova-conductor.log on a controller node. Why there is
10 matches
Mail list logo
