-
Notifications
You must be signed in to change notification settings - Fork 260
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
Update retryOnAwsCode to Five Minutes #999
Conversation
Users have been experiencing errors being returned on successful spaces create requests that take longer than 1 minute. Github issue is #996 The only child function that `resourceDigitalOceanBucketCreate` using a 1 minute timeout is the `retryOnAwsCode` so updating that to 5 minutes to hopefully mitigate the errors on successful bucket creations.
This is an odd one... The create method doesn't actually use this helper, and has its own 5 minute timeout for both the create call and polling: terraform-provider-digitalocean/digitalocean/spaces/resource_spaces_bucket.go Lines 222 to 257 in ee854f5
But I was actually able to reproduce this finally! Despite the 5 minute timeout shown above, it still times out in 1 minute. Looking at the debug logs:
The polling for the new Spaces bucket is successful. It is the step that is applying the ACLs that fails:
With this change, it eventually succeeded after 3m30s. I don't understand why Spaces is returning a successful response to |
Yes, the Spaces response is a head scratcher....but that's great you were able to reproduce it and confirm the change! Thanks Andrew! |
Users have been experiencing errors being returned on successful spaces create requests that take longer than 1 minute. Github issue is #996
The only referenced function in
resourceDigitalOceanBucketCreate
that's using a 1 minute timeout is theretryOnAwsCode
so updating that to 5 minutes to hopefully mitigate the errors on successful bucket creations.