-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nomad fails to place second allocation in basic job #14235
Comments
spotted this in a stack dump while the agent was stuck - not sure I like the coincidence of being in the same function as #14217
|
Whelp it seems we sometimes enter In the logs we see both allocs being created, entering
we apparently never return from the lookup, and never hear anything about alloc
|
This lookup issue smelled familiar, so leaving a link to this closed issue #12342 |
Yeah we've seen trouble with looking up nobody elsewhere too. On this install we have nobody in
|
Well some random googling suggests perhaps e.g. collectd/collectd#229 We could try doing a single lookup of |
Can we get away with using the |
Huh, TIL! That does actually seem to fix the problem.
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
This job reliably fails to run one of the two allocations. Using dev mode and machine has plenty of resources. The only interesting thing I can think of is it's running CentOS 9.
The job
Running the job
One of the allocs will never become healthy
Looking at the evals
Alloc status returns incomplete results
There are no WARN or ERROR statements regarding the eval/deployment/alloc.
The text was updated successfully, but these errors were encountered: