-
Notifications
You must be signed in to change notification settings - Fork 897
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 ignore errors in Vm#running_processes #17220
Don't ignore errors in Vm#running_processes #17220
Conversation
Not sure who best to review this as the code is so ancient, @bdunne what do you think? |
6ecb7ee
to
b88bc68
Compare
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 unless WMIHelper.connectServer
raises if it fails to connect...
Hm right we want it to try the next IP address, but then if they all fail we want to raise an error... |
I gave it some bogus creds and the connect doesn't fail, it does throw an exception deep down in
|
@bdunne What do you think about just raising the validation errors since that should catch most of the issues |
The Vm#running_processes method currently logs all errors/exceptions instead of raising them up. This causes the tasks to look like they were successful even though there are warnings in the log about mis-configuration which should be corrected by the user. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1534023
b88bc68
to
b187c43
Compare
Checked commit agrare@b187c43 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Thanks @bdunne ! |
…nt_eat_exception Don't ignore errors in Vm#running_processes (cherry picked from commit c6c282a) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1562780
Gaprindashvili backport details:
|
The Vm#running_processes method currently logs all errors/exceptions
instead of raising them up. This causes the tasks to look like they
were successful even though there are warnings in the log about
mis-configuration which should be corrected by the user.
The bottom two tasks were from before this change, they actually failed but look successful in the task list. The top two tasks were from after this change.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1534023