This is a bug in the provider, which should be reported in the provider's │ own issue tracker

[ravindrainduri]

Hi All,

We are using terraform in azure devops to provision aws infrastructure, essentially ECS cluster (Fargate), some how we are observing strange behaviors stating the terraform task got failed despite in back end the ECS cluster got created and ECS service is up and running. I'm attaching the screenshots for the same. Kindly help in stabilizing the code

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

Affected Resource(s)

• aws_XXXXX

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

Expected Behavior

Actual Behavior

Steps to Reproduce

1. terraform apply

Important Factoids

References

• #0000

[justinretzolk]

Hey @ravindrainduri 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you update the issue description to include the rest of the information requested in the template?

[ravindrainduri]

Hi Justin,

I'm not sure where exactly is the issue description box .

But, Our concern is we are seeing strange behaviors while running the terraform code in azure devops pipeline , and one such issue is the above error which I've pasted. So kindly help in fixing that out.

Thanks Again.

[justinretzolk]

Hey @ravindrainduri 👋 It looks like since your last comment, another issue was filed with a similar report that has a bit more information in the description. Can you take a look at #24018 and verify whether it is the same issue you're encountering?

[leonarac]

i have the same issue but in cloudfront

Error: Provider produced inconsistent final plan │ │ When expanding the plan for │ module.cloudfront.aws_cloudfront_distribution.distribution["cenanaliticos-frontend"] │ to include new values learned so far during apply, provider │ "registry.terraform.io/hashicorp/aws" produced an invalid new value for │ .default_cache_behavior[0].cache_policy_id: was null, but now │ cty.StringVal("658327ea-f89d-4fab-a63d-7e88639e58f6"). │ │ This is a bug in the provider, which should be reported in the provider's │ own issue tracker.

i´m using version = "4.30.0" hashicorp/aws

[julian-alarcon]

The CloudFront reports are probably related to this existing bug: #29234