resource/aws_ec2_transit_gateway_route_table_propagation: Error: Provider produced inconsistent result after apply - resource have been created - and TFE cannot apply again

[arnvid]

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 Version

Terraform Enterprise
0.12.28

Affected Resource(s)

aws_ec2_transit_gateway_vpc_attachment.vpc_attachment
aws_ec2_transit_gateway_route_table_propagation.route_table_propagation

Terraform Configuration Files

This is part of deploying a baseline which is deployed on account 120 so far....

Panic Output

Error: Provider produced inconsistent result after apply

When applying changes to
module.tgw-vpc-attachment.aws_ec2_transit_gateway_route_table_propagation.route_table_propagation[2],
provider "registry.terraform.io/-/aws" produced an unexpected new value for
was present, but now absent.

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

And on runs after:

module.tgw-vpc-attachment.aws_ec2_transit_gateway_vpc_attachment.vpc_attachment[0]: Modifications complete after 1s [id=tgw-attach-xxxx]
module.tgw-vpc-attachment.aws_ec2_transit_gateway_route_table_propagation.route_table_propagation[2]: Creating...

Error: error enabling EC2 Transit Gateway Route Table (tgw-rtb-xxxx) propagation (tgw-attach-xxx): TransitGatewayRouteTablePropagation.Duplicate: Propagation tgw-attach-xxx already exists in Transit Gateway Route Table tgw-rtb-xxx.
status code: 400, request id: 9a4ea138-cb93-xx-xxx-xx

on .terraform/modules/tgw-vpc-attachment/main.tf line 62, in resource "aws_ec2_transit_gateway_route_table_propagation" "route_table_propagation":
62: resource "aws_ec2_transit_gateway_route_table_propagation" "route_table_propagation" {

Expected Behavior

Transit Gateway propogation should happen and statefile should be writen

Actual Behavior

Terraform statefile thinks that the propogation is not done.

Steps to Reproduce

Not sure how to reproduce at this stage. This has been run many any times before.. rerunning the workspace does not fix it. Hopefully it will not happen on the next workspaces.. we are deploying 5-15 accounts a day..

• #0000

[mkielar]

I'm seeing similar issue with appmesh:

Error: Provider produced inconsistent result after apply
When applying changes to
module.[MASKED].module.webapp1.aws_appmesh_virtual_node.vn["green"],
provider "registry.terraform.io/-/aws" produced an unexpected new value for
was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.

The issue is quite random, and it's quite hard to reproduce, but the AWS Resource (Virtual Node in Appmesh) gets created without Terraform storing any mention of it in statefile. This causes terraform to fail on retry.

Terraform: v0.12.26
Providers:
- "aws" (hashicorp/aws) 2.70.0...
- "external" (hashicorp/external) 1.2.0...
- "null" (hashicorp/null) 2.1.2...
- "random" (hashicorp/random) 2.3.0...

Let me know if that belongs here, or you'd like another ticket specifically for AppMesh.

[mkielar]

And today with aws_vpc_endpoint_route_table_association:

Error: Provider produced inconsistent result after apply
When applying changes to
module.core_infrastructure.module.main_vpc.module.vpc.aws_vpc_endpoint_route_table_association.private_s3[0],
provider "registry.terraform.io/-/aws" produced an unexpected new value for
was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Terraform v0.12.29
Providers:
- "template" (hashicorp/template) 2.1.2
- "null" (hashicorp/null) 2.1.2
- "aws" (hashicorp/aws) 3.8.0

[mkielar]

Is this one related?
#15084

This seems to me like a general issue with AWS Provider, perhaps there should ba a centralised fix for this type of issues?

[stefangreim]

Same for aws_ec2_transit_gateway_route resource.

[ghost]

This has been released in version 3.35.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 for triage. Thanks!

[ghost]

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!