-
Notifications
You must be signed in to change notification settings - Fork 347
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
Fix errors occuring during hardware version upgrade not being reported (fixes #2001) #2010
Conversation
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 11m 32s |
1f79258
to
b782c4f
Compare
@mariolenz I'd appreciate to get this merged. |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 17s |
Sorry, I've overlooked this PR for far too long. I think we had some changes to the module. Could you please re-base your fork just to make sure there are no merge conflicts? |
b782c4f
to
b2a4a4c
Compare
@mariolenz I have rebased and checked if anything logic-wise changed that impacts this PR. That is not the case. During reviewing this, I noticed something else. Instead of propagating the error return code up the stack, , it would also be possible to change this line: community.vmware/plugins/modules/vmware_guest.py Line 1640 in b2a4a4c
to a self.module.fail_json .
Which method to fix this do you prefer? |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 4m 48s |
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
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 4m 45s |
324a44e
into
ansible-collections:main
SUMMARY Backport #2010 ISSUE TYPE Bugfix Pull Request COMPONENT NAME vmware_guest
SUMMARY
This fixes #2001.
ISSUE TYPE
COMPONENT NAME
vmware_guest