-
Notifications
You must be signed in to change notification settings - Fork 30
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
Rundeck timing out even if job is finished #14
Comments
Hey @tehsu ! Did you manage to get it working when using the |
I did, I had to use the fork from here, https://github.com/apenvern/salt-step I compiled it with some changes to the defaultReturners.yml, but it works perfectly now. I can provide the changes that I made. |
Cool! Yes, if you could provide them that would be great. Thanks! |
All you need to change is the defaultReturners.yaml, it has state.highstate: *alwaysSuccessful, copy it and change it to state.sls |
yeah, just tested and it works, thought it was something more involved :) thanks for your quick reply! almost lost a day on this :( |
better than me, I lost a week |
This needs to be merged, #19. It's the correct fix. Closing my ticket. |
I'm trying to figure out what to add to fix this issue to the returners, I figured the default ones would cover this but doesn't look like it, I added state.sls to the configuration and recompiled the jar.
[salt.state ][INFO ] {'pid': 7435, 'retcode': 0, 'stderr': '', 'stdout': '.'}
Would this parser work here?
defaultCommandParser: &defaultCommandParser !!org.rundeck.plugin.salt.output.SaltJsonReturnHandler {exitCodeKey: retcode, standardOutputKey: stdout, standardErrorKey: stderr}
The text was updated successfully, but these errors were encountered: