Error: error reading Route Table (rtb-xxx): couldn't find resource

[patrickdillon]

Terraform CLI and Terraform AWS Provider Version

v4.5.0

Affected Resource(s)

• aws_vpc_route_table

Terraform Configuration Files

It looks like this is an eventual consistency bug, so it is not easily reproduceable. I will link to our CI runs to show it happening.

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

resource "aws_route_table" "private_routes" {
  count = var.private_subnets == null ? length(var.availability_zones) : 0

  vpc_id = data.aws_vpc.cluster_vpc.id

  tags = merge(
    {
      "Name" = "${var.cluster_id}-private-${var.availability_zones[count.index]}"
    },
    var.tags,
  )
}

Source code is here.

Debug Output

An example of a CI failure with this error.

Expected Behavior

Creating route table resource should succeed. If there are failures when trying to read the newly created resource, they should be retried.

Actual Behavior

When trying to read the newly created route table, it is not found and an error is returned--rather than retrying to find the resource.

Steps to Reproduce

Unfortunately this depends on the aws backend so it is not easily reproduceable.

Important Factoids

References

• aws_ec2_route_table_association: use retry logic on newly created resource #22927 fixes several issues that are similar but for route table associations. I will open a PR momentarily to bring this same logic to route tables.

[github-actions]

This functionality has been released in v4.23.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]

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.