Do not report an error in websocket_log when closing a VNC connection #18342
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.
When closing a VNC console, the transmission block (1) can throw an
IO::WaitWritable
or with an even higher probability anIO::WaitReadable
exception. These are not inherited from theIOError
, so the cleanup will not treat this a closed exception (2) but as an error (3).The cleanup function is the same for both (2) and (3), the only difference is the way how we report them into the websocket log, That's the problem I'm trying to fix here by adding the 2 exception classes into (2).
@miq-bot add_label bug, providers/console, hammer/no
@miq-bot add_reviewer @djberg96, @kbrock @jrafanie