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 a aws_s3_bucket resource containing both versioning=true and cross-region-replication, one would expect versioning to be turned on first, as that is a requirement for cross-region-replication.
But, it seems there is a "race condition" of some sort that occasionally leads to the opposite happening, in which case an error is generated saying that cross-region-replication cannot be turned on due to lack of versioning.
Re-running terraform apply does not seem to fix things. Also, the state file seems to believe that the cross-region-replication part has already been completed. The only way we could get things to work was to turn on versioning manually in the console, then remove the replication.* attributes from the bucket resource in the state file, then rerun apply.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform version: 0.9.6
When a
aws_s3_bucket
resource containing bothversioning=true
and cross-region-replication, one would expect versioning to be turned on first, as that is a requirement for cross-region-replication.But, it seems there is a "race condition" of some sort that occasionally leads to the opposite happening, in which case an error is generated saying that cross-region-replication cannot be turned on due to lack of versioning.
Re-running terraform apply does not seem to fix things. Also, the state file seems to believe that the cross-region-replication part has already been completed. The only way we could get things to work was to turn on versioning manually in the console, then remove the
replication.*
attributes from the bucket resource in the state file, then rerunapply
.The text was updated successfully, but these errors were encountered: