-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error configuring the backend "s3": RequestError: [...] TLS handshake timeout #299
Comments
@Leichtwind @ddimitrioglo @gcaraman I'd like to propose to address this issue by retrying failed terrahub command up to 3 times with exponential backoff approach. Thoughts? |
@eistrati generally this is on terraform's side, but we can re-run |
@ddimitrioglo that's correct, something is "fishy" between terraform and s3 ... and we can open an issue to terraform, but I fear that S3 is throttling multiple parallel terraform calls to S3 backend, so I'd like to propose an improvement by catching this issue and retrying in exponential backoff manner. Does this make sense? |
@eistrati it definitely does! |
Here is another sample error:
|
Add option number of retries |
|
Same error about S3 backend here hashicorp/terraform-provider-aws#4709 |
One more use case:
|
|
Reproduced again and this time there were network connection issue and terrahub did not try to re-run . In case this will be helpful I will attach log
|
This is fixed by implementing exponential backoff for init and plan actions. |
|
Fixed in and success for the following job and configured backend: |
Checked. |
The text was updated successfully, but these errors were encountered: