-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: S3 bucket lifecycle configuration error after updating provider to 5.86.0 #41277
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Could this be related to or a duplicate of #41268? |
@baer95 it might be, the error is slightly different though, but has to do with the lifecycle. |
It's related, but a separate problem |
We have exactly the same issue. Error: Provider produced inconsistent result after apply |
This bug is now since friday. Is there any forecast when we can expect a fix? |
Hi @chelseaharalson and @tinuz74 can you please share your the full configuration of your There are several tests for both Without a way to reproduce the problem that you're reporting, we won't be able to fix it. |
I did not change the configuration before or after the upgrade. This is the error message: |
Hi, See config below. Also nothing changed with the code before or after the upgrade.
} dynamic "rule" {
} |
@gdavison This is also affecting our org, with similar issues as the other posters above - no changes to config, applied 5.85.0, then 5.86.0, and now on 5.86.1. It's now giving the same error as above - I've attached some debug logs below, considering the full output is massive and there's some concerns about data leaks by posting the full debug log; let me know if there's anything in particular you're looking for. I can also grab all logs for the tf_req_id if you'd like, but again, probably more than I can paste here. Plan logs:
Apply logs:
Full source:
|
Hi,
We are getting this error after the terraform-provider-aws update to 5.86.0:
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ aws_s3_bucket_lifecycle_configuration.availability_service_s3_bucket_lifecycle_configuration,
│ provider "provider["registry.terraform.io/hashicorp/aws"]" produced an
│ unexpected new value: .rule[0].expiration[0].expired_object_delete_marker:
│ was cty.True, but now cty.False.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
The text was updated successfully, but these errors were encountered: