[integ-tests-framework] Fix SSH banner timeout when using bastion gateway in RemoteCommandExecutor#7338
Merged
hanwen-cluster merged 2 commits intoaws:developfrom Apr 15, 2026
Merged
Conversation
…eway in RemoteCommandExecutor
The SSH gateway command used for bastion connections was missing -o StrictHostKeyChecking=no and -i {cluster.ssh_key}. When the bastion host key was not in known_hosts, the gateway ssh process would prompt interactively for host key verification. Since paramiko runs this process non-interactively, the prompt blocks stdin indefinitely, preventing the SSH banner from reaching paramiko and causing a paramiko.ssh_exception.SSHException: Error reading SSH protocol banner after the 60-second banner timeout.
This only manifested in environments where ~/.ssh/config did not already set StrictHostKeyChecking no globally. Environments that had this configured (or had the bastion host already in known_hosts) were unaffected.
hehe7318
approved these changes
Apr 15, 2026
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
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.
Description of changes
The SSH gateway command used for bastion connections was missing -o StrictHostKeyChecking=no and -i {cluster.ssh_key}. When the bastion host key was not in known_hosts, the gateway ssh process would prompt interactively for host key verification. Since paramiko runs this process non-interactively, the prompt blocks stdin indefinitely, preventing the SSH banner from reaching paramiko and causing a paramiko.ssh_exception.SSHException: Error reading SSH protocol banner after the 60-second banner timeout.
This only manifested in environments where ~/.ssh/config did not already set StrictHostKeyChecking no globally. Environments that had this configured (or had the bastion host already in known_hosts) were unaffected.
Tests
The following tests have passed:
Checklist
developadd the branch name as prefix in the PR title (e.g.[release-3.6]).Please review the guidelines for contributing and Pull Request Instructions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.