module.networking.aws_default_route_table Error: Provider produced inconsistent result after apply #9009

mariaiano · 2019-06-16T19:59:53Z

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 "me too" comments, 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 v0.12.2

provider.aws v2.15.0

Affected Resource(s)

aws_default_route_table

Terraform Configuration Files

# 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

https://drive.google.com/open?id=1V0bn0OpZ8jrLKmml6XYUSSk7gQz8bxAN

Debug Output

https://drive.google.com/open?id=17udS9g1dBo3uI-IhkI2tr9Nbz_9B0UEr

Panic Output

Expected Behavior

module.networking.aws_default_route_table.dio_private_rt should have been created.

Actual Behavior

Instead I got this error:

Error: Provider produced inconsistent result after apply

When applying changes to
module.networking.aws_default_route_table.dio_private_rt, provider "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.

Steps to Reproduce

terraform apply

Important Factoids

References

#0000

The text was updated successfully, but these errors were encountered:

mariaiano · 2019-07-24T14:53:30Z

I wonder why there aren't more people reporting this. Is there some workaround I'm missing?

FernandoMiguel · 2019-08-05T09:30:17Z

@mariaiano i get this all the time :(
aws_cloudwatch_log_stream.log-stream, provider "aws" produced an unexpected new value for was present, but now absent.

tiny-dancer · 2019-08-09T19:43:58Z

we're seeing this as well, starting to wrap TF in retries.

When applying changes to aws_vpc_endpoint_route_table_association.db_s3[1], provider "aws" produced an unexpected new value for was present, but now absent

hotdawg789 · 2019-09-09T15:23:00Z

Similar response with provider "aws" (hashicorp/aws) 2.25.0.

Error: Provider produced inconsistent result after apply

When applying changes to
aws_vpc_endpoint_route_table_association.pub_rancher_us-east-1a, provider
"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.

jayalane · 2019-11-21T23:02:04Z

I think most people don't use default route table, perhaps because of this. The extra route tables (one default, one made by terraform) is confusing but functional.

jayalane · 2019-11-22T00:43:32Z

Ah, I have it: if you specify the VPC this way:

default_route_table_id = aws_vpc.whatever_vpc.id

You get that (which will happen if change aws_route_table to default_route table and then change the key from vpc_id but not the value).

You want

default_route_table_id = aws_vpc.whatever_vpc.default_route_table.id

bflad · 2019-11-22T19:15:24Z

Hi folks 👋 Sorry you are running into this. Please note I've marked this issue as a bug, but we would prefer to capture each different Terraform resource reporting this error in separate bug reports. Each Terraform resource that hits this error will be due to different code and API behaviors. We are going to treat this report just for the original report of the aws_default_route_table resource.

The errant code can be found here: https://github.com/terraform-providers/terraform-provider-aws/blob/101295fdf4b62139d82808d43fd04d84bd1bb435/aws/resource_aws_default_route_table.go#L112-L116

In the Create function for the resource, we are returning an empty resource when no default route table is found where we should instead error in this scenario. The error message we can return can be much more helpful to the operator. 👍

I'll submit the fix for this shortly.

…ehavior when Default Route Table is missing Reference: #398 Reference: #3551 Reference: #9009 Previously on creation, if the Default Route Table was incorrectly configured or non-existent, the resource would unexpectedly attempt to remove itself from the Terraform state and propose recreation immediately. Prior to Terraform 0.12, this behavior was errantly acceptable. In Terraform 0.12, resources are required to return Terraform state about themselves during creation or throw an error explaining why the creation failed. Previously on read, if the Default Route Table was missing (e.g. due to the VPC being deleted outside Terraform), the resource would return an error and require operators to manually perform a `terraform state rm` command instead of proposing resource recreation. Output from new acceptance testing before code updates: ``` --- FAIL: TestAccAWSDefaultRouteTable_basic (20.02s) testing.go:628: Step 0, expected error: errors during apply: Provider produced inconsistent result after apply: When applying changes to aws_default_route_table.foo, provider "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. To match: TBD --- FAIL: TestAccAWSDefaultRouteTable_disappears_Vpc (20.27s) testing.go:635: Step 0 error: errors during follow-up refresh: Error: Default Route table not found testing.go:696: Error destroying resource! WARNING: Dangling resources may exist. The full state and error is shown below. Error: errors during refresh: Default Route table not found State: <nil> ``` Output from acceptance testing after code updates: ``` --- PASS: TestAccAWSDefaultRouteTable_disappears_Vpc (20.46s) --- PASS: TestAccAWSDefaultRouteTable_basic (40.99s) --- PASS: TestAccAWSDefaultRouteTable_vpc_endpoint (49.71s) --- PASS: TestAccAWSDefaultRouteTable_swap (73.89s) --- PASS: TestAccAWSDefaultRouteTable_Route (87.09s) --- PASS: TestAccAWSDefaultRouteTable_Route_TransitGatewayID (374.87s) ```

…ehavior when Default Route Table is missing (#10981) Reference: #398 Reference: #3551 Reference: #9009 Previously on creation, if the Default Route Table was incorrectly configured or non-existent, the resource would unexpectedly attempt to remove itself from the Terraform state and propose recreation immediately. Prior to Terraform 0.12, this behavior was errantly acceptable. In Terraform 0.12, resources are required to return Terraform state about themselves during creation or throw an error explaining why the creation failed. Previously on read, if the Default Route Table was missing (e.g. due to the VPC being deleted outside Terraform), the resource would return an error and require operators to manually perform a `terraform state rm` command instead of proposing resource recreation. Output from new acceptance testing before code updates: ``` --- FAIL: TestAccAWSDefaultRouteTable_basic (20.02s) testing.go:628: Step 0, expected error: errors during apply: Provider produced inconsistent result after apply: When applying changes to aws_default_route_table.foo, provider "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. To match: TBD --- FAIL: TestAccAWSDefaultRouteTable_disappears_Vpc (20.27s) testing.go:635: Step 0 error: errors during follow-up refresh: Error: Default Route table not found testing.go:696: Error destroying resource! WARNING: Dangling resources may exist. The full state and error is shown below. Error: errors during refresh: Default Route table not found State: <nil> ``` Output from acceptance testing after code updates: ``` --- PASS: TestAccAWSDefaultRouteTable_disappears_Vpc (20.46s) --- PASS: TestAccAWSDefaultRouteTable_basic (40.99s) --- PASS: TestAccAWSDefaultRouteTable_vpc_endpoint (49.71s) --- PASS: TestAccAWSDefaultRouteTable_swap (73.89s) --- PASS: TestAccAWSDefaultRouteTable_Route (87.09s) --- PASS: TestAccAWSDefaultRouteTable_Route_TransitGatewayID (374.87s) ```

bflad · 2019-11-25T16:09:17Z

The adjustment of the aws_default_route_table resource to return a more helpful error in this scenario has been merged and will release with version 2.40.0 of the Terraform AWS Provider this week. If you are seeing the Provider produced inconsistent result after apply with other resources (or this resource after this fix is released) please submit a new bug report following the issue template for further triage. Thanks.

ghost · 2019-11-27T00:03:28Z

This has been released in version 2.40.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 · 2020-03-29T17:11:33Z

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!

aeschright added the needs-triage Waiting for first response or review from a maintainer. label Jun 19, 2019

aeschright added the service/ec2 Issues and PRs that pertain to the ec2 service. label Jul 3, 2019

bflad added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 22, 2019

bflad mentioned this issue Nov 22, 2019

resource/aws_default_route_table: Fixes for creation and recreation behavior when Default Route Table is missing #10981

Merged

bflad added this to the v2.40.0 milestone Nov 25, 2019

bflad closed this as completed in #10981 Nov 25, 2019

ghost locked and limited conversation to collaborators Mar 29, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

module.networking.aws_default_route_table Error: Provider produced inconsistent result after apply #9009

module.networking.aws_default_route_table Error: Provider produced inconsistent result after apply #9009

mariaiano commented Jun 16, 2019

mariaiano commented Jul 24, 2019

FernandoMiguel commented Aug 5, 2019

tiny-dancer commented Aug 9, 2019

hotdawg789 commented Sep 9, 2019 •

edited

Loading

jayalane commented Nov 21, 2019

jayalane commented Nov 22, 2019

bflad commented Nov 22, 2019

bflad commented Nov 25, 2019

ghost commented Nov 27, 2019

ghost commented Mar 29, 2020

module.networking.aws_default_route_table Error: Provider produced inconsistent result after apply #9009

module.networking.aws_default_route_table Error: Provider produced inconsistent result after apply #9009

Comments

mariaiano commented Jun 16, 2019

Community Note

Terraform Version

Affected Resource(s)

Terraform Configuration Files

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Important Factoids

References

mariaiano commented Jul 24, 2019

FernandoMiguel commented Aug 5, 2019

tiny-dancer commented Aug 9, 2019

hotdawg789 commented Sep 9, 2019 • edited Loading

jayalane commented Nov 21, 2019

jayalane commented Nov 22, 2019

bflad commented Nov 22, 2019

bflad commented Nov 25, 2019

ghost commented Nov 27, 2019

ghost commented Mar 29, 2020

hotdawg789 commented Sep 9, 2019 •

edited

Loading