You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use the JavaScript AWS S3 API to create a bucket and add a bucket policy to this bucket, everything works immediately. I can then get the bucket as well it's bucket policy.
When I create another bucket with JavaScript AWS S3 API, and then use the s3cmdinfo on this bucket, I get a 404 NoSuchBucket error. And after about a minute I get the bucket info. I dug into the code for s3cmd, and it seems that it does to check if a bucket is available is a HTTPS call to the URL:
and this returns a HTTP 404 NoSuchBucket. What is unclear to me is why the S3 API gives a result, but calling the URL on digitaloceanspaces.com produces a 404 that eventually gives a 200. Eventually = about 1-2 minutes, sometimes longer.
This is affecting me as well @srasul . Has there been a fix or work around? @andrewsomething can you take a look at this? This is blocking creation of DO spaces via Terraform.
@nkotixwolf unfortunately I couldn't find a solution to this. My current workaround is to move the creation of the bucket out of Terraform and into additional code that runs before Terraform. Once the bucket is created, I pass the name of this bucket into Terraform as an input parameter so other Terraform resources can use it.
Bug Report
Describe the bug
When creating a Spaces Bucket via Terraform, we get a timeout and and the following error:
Error: NoSuchBucket: status code: 404, request id:
Affected Resource(s)
Expected Behavior
The bucket should be created sucessfully
Actual Behavior
There is a timout waiting for the bucket to be created.
I went to the Digital Ocean web console and could see the Bucket was there, but Terraform was still waiting for this bucket to be created.
Steps to Reproduce
Terraform Configuration Files
Terraform version
2.34.1
Debug Output
Panic Output
Additional context
We are 'applying' via Terraform Cloud.
Important Factoids
References
The text was updated successfully, but these errors were encountered: