-
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 0.12.4 stop allocation issue #8866
Comments
Hi @roman-vynar ! Thanks for reaching out! I'm investigating this but sadly unable to reproduce it - can you please provide more detailed instructions along with sample output and logs? Here is my attempt at reproduction - not that it only has a single running alloc at the end. Script
|
Back to 0.12.4. It is constantly reproducible:
Notice the following message from stop command:
Job def specs what applicable:
5m later it is still running:
Please let me know if you need anything else. |
Thank you very much for the report. I have confirmed the problem and pushed a solution to rollback to old canary behavior to avoid this regression. It seems that it disproportionately affect single alloc service jobs with canary deployments. |
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.12.4 (both servers/clients)
Issue
I have a "service" type job running with count=1.
When I stop an alloc, Nomad starts 2 new allocs instead.
It was ok on 0.12.1.
Reverted back to 0.12.1 (servers/clients) and the behaviour changed back to normal - you stop an alloc and Nomad starts 1 alloc.
The text was updated successfully, but these errors were encountered: