-
Notifications
You must be signed in to change notification settings - Fork 900
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
don't call postprocess without job in playbook on_error #20773
Conversation
@tinaafitz please review |
239d9ad
to
574fcd9
Compare
Checked commit d-m-u@574fcd9 with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @d-m-u.
@djberg96 Please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@d-m-u Can this be |
@miq-bot add_label ivanchuk/yes |
don't call postprocess without job in playbook on_error (cherry picked from commit 19f3728) https://bugzilla.redhat.com/show_bug.cgi?id=1835226
Ivanchuk backport details:
|
don't call postprocess without job in playbook on_error (cherry picked from commit 19f3728)
Jansa backport details:
|
don't call postprocess without job in playbook on_error (cherry picked from commit 19f3728)
Kasparov backport details:
|
playbook postprocessing shouldn't happen if the job is nil in
on_error
since having a nil job is a potential outcome of the valid scenarios we're trying to handle with the retry of ansible playbook connection stuff (see the related pr), we also need to handle this logic branch
related to the work done on #20738