builder/amazonebs: Move SSH.new into ConnectWaitLoop #138
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.
EC2 images can sometimes accept a connection on port 22 without
truly being ready to complete SSH. For example, it may not complete
the full hand-shake (closing the connection immediately) or it may
not have the appropriate public keys in place. The prior code
would only attempt an SSH handshake once, which would unnecessarily
fail the build in these instances.
Fix #130 by moving SSH.new into the loop that retries connections,
and improve debuggability by logging the failure causes on each
connection fail.
Signed-off-by: Emil Sit [email protected]