handle retriable ssh dial error#4570
Open
jgao54 wants to merge 1 commit into
Open
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Wrap ssh tunnel
DialContextinSSHTunnelDialErrorand classify it accordingly.The error we saw:
This can happen when SSH connection is torn down while a channel open is in flight. If the tunnel's TCP connection dies before the reply arrives from the bastion server, x/crypto/ssh's mux teardown closes the pending reply channel, and the nil message read from it formats as
<nil>.We observed this to have recovered on its own; if the bastion server is permanently down; the next attempt would fail with
SSHTunnelSetupErrorinstead and notify user.Fixes: DBI-854