-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Job run CLI exit code is zero even when deployment fails #11708
Comments
Hi @martinmcnulty 👋 I believe this was fixed in #11550 and will ship in our next release, so I'm going to close this one for now but let us know if that fix is not what you are looking for. |
Hi @lgfa29 :) Thanks for that - that PR sounds like exactly what I'm looking for! Sorry, not sure how I missed the existing issues when I searched (maybe I only searched for open ones? Who knows....) Anyway, thanks again. Look forward to the next release! |
No worries. It's always hard to keep up with issues and PRs. We appreciate you reaching out and providing such a detailed issue report ❤️ |
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
Nomad v1.2.3 (a79efc8422082c4790046c3f5ad92c542592a54f)
Operating system and Environment details
Issue
When using
nomad job run
to trigger a deployment, if the deployment fails, the command still exits with a zero exit code, making it difficult to detect problems in shell scripts.Reproduction steps
nomad job run
echo $?
Expected Result
Exit code should be 1 on a deployment failure, according to the docs:
Actual Result
Exit code is 0:
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: