Closed ghost closed 5 years ago
Hi @Prashantpv 👋 Sorry you ran into this confusing error and thank you for reporting it. There have been a lot of relevant changes in the Terraform Core and Terraform AWS Provider codebases since this issue was originally reported so as a first step it might be best to try updating to recent versions of both and seeing if any of those updates may have resolved this issue.
Attempting to troubleshoot these types of errors is very difficult in Terraform 0.11 and earlier as those versions will report this problem (diffs didn't match during apply
error) where a problematic configuration value exists or is referenced and not where the Terraform resource with the underlying problem actually exists. We typically will need much more information than the original error message suggests for filing the issue (e.g. the full Terraform configuration). There are also frequent issues in the Terraform 0.11 error reporting where the error message is due to behavior outside the control of the Terraform resources themselves (e.g. lifecycle
configurations).
In Terraform 0.12 and later, the "value did not match" type of error can now be found with the newer Provider produced inconsistent result after apply
error, which better reports the source of the problem so the provider maintainers and community can more easily work towards a fix of the issue. Other similar errors that fell previously into diffs didn't match during apply
errors, but outside problems within the Terraform provider are also better diagnosed before being displayed.
Since the majority of the Terraform code path and reporting structure of these errors has changed between Terraform 0.11 and 0.12, along with the difficult triage process in Terraform 0.11 and earlier, the maintainers prefer to close these older issues to continue troubleshooting and fixing based on Terraform 0.12's error reporting instead. I apologize for this unsatisfying closure of this particular version of the issue.
That said, if the configuration does happen to reproduce the newer Provider produced inconsistent result after apply
error in Terraform 0.12 (which requires Terraform AWS Provider version 2.7.0 or later), please do not hesitate to file a new issue and complete all of the information requested in the Bug Report template so we can hopefully get the root cause for fixing the issue. Thanks again for this bug report and sorry about the additional steps for getting a potential fix implemented.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
This issue was originally opened by @Prashantpv as hashicorp/terraform#18493. It was migrated here as a result of the provider split. The original body of the issue is below.
We are using terraform to provision our end to end infrastructure on AWS. We have written modules for VPC, Private Subnet, Public Subnet and many more. Everything was working fine until yesterday but now we are facing some issue with aws_network_acl resource wherein on every terraform apply, its showing there are some updates which are false positive (no changes at rest). Below is the error which we are facing:
module.private_subnet.aws_network_acl.app: aws_network_acl.app: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue. Provider info and diff:
Terraform Version: 0.11.7 Resource ID: aws_network_acl.app Mismatch reason: attribute mismatch: egress.1222510970.cidr_block
_Private Subnet Module:_
main.tf:
acl.tf
data_source.tf
input .tf file