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

Error: Inconsistent final plan in aws_route_table #19133

Closed
matt-slalom opened this issue Apr 27, 2021 · 5 comments · Fixed by #19426
Closed

Error: Inconsistent final plan in aws_route_table #19133

matt-slalom opened this issue Apr 27, 2021 · 5 comments · Fixed by #19426
Assignees
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@matt-slalom
Copy link

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 v0.14.11

  • provider registry.terraform.io/hashicorp/aws v3.37.0

Affected Resource(s)

  • aws_route_table

Terraform Configuration Files

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

Gist with the code to reproduce the error: https://gist.github.com/matt-slalom/c09df4db8147cc394da27a1a4c0a7e82

Debug Output

Gist for debug output: https://gist.github.com/matt-slalom/6c6901a9b9ffaab1485ddacde9c33341

Expected Behavior

Actual Behavior

The first run results in an error. Running apply a second time successfully completes.

Error: Provider produced inconsistent final plan

When expanding the plan for
aws_route_table.the_private_route_table["vpc1-private-1B"] to include new
values learned so far during apply, provider
"registry.terraform.io/hashicorp/aws" produced an invalid new value for
.route: was known, but now unknown.

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

Steps to Reproduce

  1. terraform apply to the code in the gist: https://gist.github.com/matt-slalom/c09df4db8147cc394da27a1a4c0a7e82

Important Factoids

None

References

None

@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Apr 27, 2021
@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 Apr 27, 2021
@matt-slalom
Copy link
Author

This is 100% reproducible, and since the output says it's an error, I'm reporting it. If this is due to something I'm doing wrong, please let me know!

@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Apr 28, 2021
@ewbankkit
Copy link
Contributor

ewbankkit commented Apr 28, 2021

@matt-slalom Thanks for raising this issue.
I can reproduce in our test environment using your provided configuration (with the latest Terraform version v0.15.1).

@ewbankkit
Copy link
Contributor

May be related to calling d.Set("route") in resourceAwsRouteTableUpdate():

@github-actions
Copy link

This functionality has been released in v3.47.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 Jul 25, 2021
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/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
2 participants