Skip to content
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

Issue with S3 Replication V2 with Version 4 of AWS #23551

Closed
narrarajesh opened this issue Mar 7, 2022 · 3 comments · Fixed by #23586
Closed

Issue with S3 Replication V2 with Version 4 of AWS #23551

narrarajesh opened this issue Mar 7, 2022 · 3 comments · Fixed by #23586
Labels
bug Addresses a defect in current functionality. service/s3 Issues and PRs that pertain to the s3 service.
Milestone

Comments

@narrarajesh
Copy link

narrarajesh commented Mar 7, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.1.5
on windows_amd64

  • provider registry.terraform.io/hashicorp/aws v4.4.0
  • provider registry.terraform.io/hashicorp/null v3.1.0
  • provider registry.terraform.io/hashicorp/vault v3.3.1

Affected Resource(s)

S3 - Cross Region Replication

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Panic Output

Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for
│ module.buckent-nd-kms["pcu"].aws_s3_bucket_replication_configuration.replication
│ to include new values learned so far during apply, provider
│ "registry.terraform.io/hashicorp/aws" produced an invalid new value for
│ .rule: planned set element
│ cty.ObjectVal(map[string]cty.Value{"delete_marker_replication":cty.ListValEmpty(cty.Object(map[string]cty.Type{"status":cty.String})),
│ "destination":cty.ListValEmpty(cty.Object(map[string]cty.Type{"access_control_translation":cty.List(cty.Object(map[string]cty.Type{"owner":cty.String})),
│ "account":cty.String, "bucket":cty.String,
│ "encryption_configuration":cty.List(cty.Object(map[string]cty.Type{"replica_kms_key_id":cty.String})),
│ "metrics":cty.List(cty.Object(map[string]cty.Type{"event_threshold":cty.List(cty.Object(map[string]cty.Type{"minutes":cty.Number})),
│ "status":cty.String})),
│ "replication_time":cty.List(cty.Object(map[string]cty.Type{"status":cty.String,
│ "time":cty.List(cty.Object(map[string]cty.Type{"minutes":cty.Number}))})),
│ "storage_class":cty.String})),
│ "existing_object_replication":cty.ListValEmpty(cty.Object(map[string]cty.Type{"status":cty.String})),
│ "filter":cty.ListValEmpty(cty.Object(map[string]cty.Type{"and":cty.List(cty.Object(map[string]cty.Type{"prefix":cty.String,
│ "tags":cty.Map(cty.String)})), "prefix":cty.String,
│ "tag":cty.List(cty.Object(map[string]cty.Type{"key":cty.String,
│ "value":cty.String}))})), "id":cty.NullVal(cty.String),
│ "prefix":cty.NullVal(cty.String), "priority":cty.NullVal(cty.Number),
│ "source_selection_criteria":cty.ListValEmpty(cty.Object(map[string]cty.Type{"replica_modifications":cty.List(cty.Object(map[string]cty.Type{"status":cty.String})),
│ "sse_kms_encrypted_objects":cty.List(cty.Object(map[string]cty.Type{"status":cty.String}))})),
│ "status":cty.NullVal(cty.String)}) does not correlate with any element in
│ actual.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

Expected Behavior

Issue is with S3 v2 cross region replication. it is creating the replication in first apply okay but after every other run, getting the above error. this is not an issue in V1 of replication.

Actual Behavior

Issue is with S3 v2 cross region replication. it is creating the replication in first apply okay but after every other run, getting the above error. this is not an issue in V1 of replication.

Steps to Reproduce

  1. terraform apply

Important Factoids

References

  • #0000
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. bug Addresses a defect in current functionality. labels Mar 7, 2022
@anGie44
Copy link
Contributor

anGie44 commented Mar 7, 2022

Hi @narrarajesh , thank you for raising this issue.
Just noting here that it looks very similar to #23487

Do you mind filling out the Terraform Configuration Files section with as much information as possible?

@anGie44 anGie44 added service/s3 Issues and PRs that pertain to the s3 service. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 7, 2022
@github-actions github-actions bot added this to the v4.5.0 milestone Mar 10, 2022
@github-actions
Copy link

This functionality has been released in v4.5.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/s3 Issues and PRs that pertain to the s3 service.
Projects
None yet
2 participants