-
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
System jobs don't start on new agents #6089
Comments
The job should automatically start if the resources are available on the new client node and the system job isn't filtered by constraints. When you check the status of the job, does it show blocked allocations? |
I resubmitted the Fabio job and it began to run on all nodes. This may have been a consul acl issue, since I forgot to add a consul role to the nomad worker. Whatever the root cause was, I can no longer reproduce the issue. |
I've upgraded to nomad 0.10.4 and added a new nomad agent and I find that the 'fabio' job does not get scheduled to this agent. Several days have passed, and other batch jobs are running successfully, but the system job fabio still hasn't started. |
Hey! Sorry this has come up again. There's nothing obvious in that job file that would prevent it from running. Could you provide the output of |
I think this may have been fixed by this PR - #11054 Going to close this out, as its been a while and this PR or others that have shipped in the meantime have likely fixed it. Please re-open if that is not the case! |
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. |
Nomad version 0.9.4
I have fabio running as a system job in my nomad cluster.
When I add new nomad agents, the system job does not start automatically.
According to the docs
The nomad agent is in 'ready' state.
There are no errors in the logs
Is this expected behavior? Or should the job automatically start?
The text was updated successfully, but these errors were encountered: