-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Return system exit codes on failures #14435
Comments
Pretty sure #11337 fixes this issue, but those changes do not exist in the current release of salt, they will be in the next feature release (2014.7.0) which should go into release candidate very very soon, and full release in a month or two. |
Would you mind testing on the develop branch or the 2014.7 branch to verify? |
Sure thing. I will look at it today/tomorrow. On Wed, Jul 23, 2014 at 7:11 PM, Colton Myers notifications@github.com
|
Some quick testing and it looks like its working. I will do some more indepth with my own states when I can put more time into it. Guess I need to upgrade soon. What's the timeline for release?
|
We should have 2014.7.0rc1 out first thing next week, and the final release is expected 4-6 weeks after that, depending on how the release candidate is received. |
I'm going to close this, since it's been implemented. |
Please re-open this bug. It still exists in
I'm also linking it to #18510 - an "umbrella" issue for many other expected non-zero codes. It is easily reproducible:
|
Thanks for updating us here @uvsmtid. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
When executing salt states or modules from the command line, it would be extremely helpful for it to return standard system exit codes.
When combined with other automation pieces, it is impossible to catch any possible errors. I have seen other reasons why there are no codes returned, but as OPS using this tool, I need to know if something went wrong. Anything non-zero would be ok.
For example, when an SLS is not found.
But, when no minions match a glob?
The text was updated successfully, but these errors were encountered: