Add more robust error handling to ConversionHost#get_conversion_state #18258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on a conversation with Kedar Kulkarni, this PR attempts to add some more robust error handling to the
get_conversion_state
method. At the moment the SFTP download is sometimes failing somehow, so the data stream ends up being blank, which then results in a JSON parser error. This doesn't tell us the "real" error, which I'm hoping to figure out.Original reported at https://bugzilla.redhat.com/show_bug.cgi?id=1653407 (but don't use this)
(The other micro changes you see were already-existent blank spaces that were auto-stripped by my editor, I'm surprised rubocop didn't catch those before).WIP for now as I'm not sure that this will be enough, or if MiqSshUtil (from gems-pending) needs some TLC.https://bugzilla.redhat.com/show_bug.cgi?id=1695847