-
Notifications
You must be signed in to change notification settings - Fork 80
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
Handle failure codes as failures #20
Labels
Comments
What playbook were you running? I agree error detection can be improved. Pull requests are welcome :) |
I should have something later :) |
Working on catching failures, should have it committed by end of day 10.02 |
Try again with latest commit. All existing functions now handle most error codes correctly. |
If problem persists, please reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like a lot of failure codes aren't picked up as module failures, and thus treat the host as "ok" despite nothing working - i.e. this 401 error shows as green:
ok: [fresh.nodes -> provisioning] => {"changed": false, "failed": false, "result": 401}
The text was updated successfully, but these errors were encountered: