RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS #21683

ellisroll-b · 2021-11-08T17:45:09Z

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 1.0.1 linux amd64

Installed hashicorp/aws v3.64.2 (signed by HashiCorp)
Installed hashicorp/random v3.1.0 (signed by HashiCorp)
Installed hashicorp/time v0.7.2 (signed by HashiCorp)

Affected Resource(s)

aws_route_table_association

Terraform Configuration Files

Associated routing resources (sans VPC, subnets, internet-gateway, and nat)

//-----------------------------------------------------------
// public route table and internet gateway route
//-----------------------------------------------------------
resource "aws_route_table" "publicRouteTable" {
  vpc_id = aws_vpc.mainVPC.id
  tags = {
    Name    = "${var.environmentName} Public route table"
  }
}

//note that tags are not allowed on a route
resource "aws_route" "publicInternetGatewayRoute" {
  route_table_id = aws_route_table.publicRouteTable.id
  destination_cidr_block = "0.0.0.0/0"
  gateway_id = aws_internet_gateway.mainIG.id
  timeouts {
    create = "6m"
  }
}

//-----------------------------------------------------------
// private route table and nat gateway route
//-----------------------------------------------------------
resource "aws_route_table" "privateRouteTable" {
  vpc_id = aws_vpc.mainVPC.id
  tags = {
    Name    = "${var.environmentName} Private route table"
  }
}

//note that tags are not allowed on a route
resource "aws_route" "privateNatGatewayRoute" {
  route_table_id          = aws_route_table.privateRouteTable.id
  destination_cidr_block  = "0.0.0.0/0"
  nat_gateway_id          = aws_nat_gateway.natGateway.id
  timeouts {
    create = "6m"
  }
}


//-----------------------------------------------------------
// route table associations
//-----------------------------------------------------------
resource "time_sleep" "waitRouteTableElements" {
  depends_on = [
    aws_route_table.publicRouteTable,
    aws_route.publicInternetGatewayRoute,
    aws_route_table.privateRouteTable,
    aws_route.privateNatGatewayRoute,
    aws_subnet.publicSubNet1,
    aws_subnet.publicSubNet2,
    aws_subnet.privateSubNet1,
    aws_subnet.privateSubNet2
  ]
  create_duration = "6m"
}

resource "aws_route_table_association" "public1" {
  depends_on     = [time_sleep.waitRouteTableElements]
  subnet_id      = aws_subnet.publicSubNet1.id
  route_table_id = aws_route_table.publicRouteTable.id
}

resource "aws_route_table_association" "public2" {
  depends_on     = [time_sleep.waitRouteTableElements]
  subnet_id      = aws_subnet.publicSubNet2.id
  route_table_id = aws_route_table.publicRouteTable.id
}

resource "aws_route_table_association" "private1" {
  depends_on     = [time_sleep.waitRouteTableElements]
  subnet_id      = aws_subnet.privateSubNet1.id
  route_table_id = aws_route_table.privateRouteTable.id
}

resource "aws_route_table_association" "private2" {
  depends_on     = [time_sleep.waitRouteTableElements]
  subnet_id      = aws_subnet.privateSubNet2.id
  route_table_id = aws_route_table.privateRouteTable.id
}

Debug Output

Panic Output

Expected Behavior

Identified that AWS reported the association was complete, and not failed the apply.

Actual Behavior

Looks like it might not be waiting long enough. Loops waiting for DescribeRouteTables to indicate associated:

<AssociateRouteTableResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
    <requestId>aea99d68-b36e-4fe7-b267-d91e827d285a</requestId>
    <associationId>rtbassoc-07d32038d3161359d</associationId>
    <associationState>
        <state>associated</state>
    </associationState>
</AssociateRouteTableResponse>: timestamp=2021-11-08T11:30:07.613-0500
2021-11-08T11:30:07.613-0500 [INFO]  provider.terraform-provider-aws_v3.64.2_x5: 2021/11/08 11:30:07 [DEBUG] Waiting for Route Table Association (rtbassoc-07d32038d3161359d) creation: timestamp=2021-11-08T11:30:07.613-0500
2021-11-08T11:30:07.613-0500 [INFO]  provider.terraform-provider-aws_v3.64.2_x5: 2021/11/08 11:30:07 [DEBUG] Waiting for state to become: [associated]: timestamp=2021-11-08T11:30:07.613-0500
2021-11-08T11:30:07.614-0500 [INFO]  provider.terraform-provider-aws_v3.64.2_x5: 2021/11/08 11:30:07 [DEBUG] [aws-sdk-go] DEBUG: Request ec2/DescribeRouteTables Details:

-----------------------------------------------------: timestamp=2021-11-08T11:30:07.760-0500
2021-11-08T11:30:07.789-0500 [INFO]  provider.terraform-provider-aws_v3.64.2_x5: 2021/11/08 11:30:07 [DEBUG] [aws-sdk-go] DEBUG: Response ec2/DescribeRouteTables Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 200 OK

Gets a payload response that indicates its associated:

<DescribeRouteTablesResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
    <requestId>d8bec8c3-4a8a-45ba-8420-cdf7d1354e31</requestId>
    <routeTableSet>
        <item>
            <routeTableId>rtb-0a8ba52dfbbdc7717</routeTableId>
            <vpcId>vpc-06f9c23d15c361252</vpcId>
            <ownerId>#######</ownerId>
            <routeSet>
                <item>
                    <destinationCidrBlock>10.100.0.0/16</destinationCidrBlock>
                    <gatewayId>local</gatewayId>
                    <state>active</state>
                    <origin>CreateRouteTable</origin>
                </item>
                <item>
                    <destinationCidrBlock>0.0.0.0/0</destinationCidrBlock>
                    <gatewayId>igw-0c8ab62f7a92f1c37</gatewayId>
                    <state>active</state>
                    <origin>CreateRoute</origin>
                </item>
            </routeSet>
            <associationSet>
                <item>
                    <routeTableAssociationId>rtbassoc-099a83c99f258c36f</routeTableAssociationId>
                    <routeTableId>rtb-0a8ba52dfbbdc7717</routeTableId>
                    <subnetId>subnet-0fc53a3b7ebe19d64</subnetId>
                    <main>false</main>
                    <associationState>
                        <state>associated</state>
                    </associationState>
                </item>
                <item>
                    <routeTableAssociationId>rtbassoc-0dcdc8c9a5e92d331</routeTableAssociationId>
                    <routeTableId>rtb-0a8ba52dfbbdc7717</routeTableId>
                    <subnetId>subnet-00621c15caee268dc</subnetId>
                    <main>false</main>
                    <associationState>
                        <state>associated</state>
                    </associationState>
                </item>
            </associationSet>
            <propagatingVgwSet/>
            <tagSet>
                <item>
                    <key>User</key>
                    <value>####</value>
                </item>
                <item>
                    <key>Name</key>
                    <value>#### Public route table</value>
                </item>
                <item>
                    <key>Domain</key>
                    <value>####</value>
                </item>
                <item>
                    <key>Billing</key>
                    <value>####</value>
                </item>
            </tagSet>
        </item>
    </routeTableSet>
</DescribeRouteTablesResponse>: timestamp=2021-11-08T11:30:07.789-0500
2021-11-08T11:30:07.790-0500 [INFO]  provider.terraform-provider-aws_v3.64.2_x5: 2021/11/08 11:30:07 [DEBUG] [aws-sdk-go] DEBUG: Request ec2/DescribeRouteTables Details:

but then it fails with : empty result

module.network.aws_route_table_association.private1: Creating...
module.network.aws_route_table_association.private2: Creation complete after 1s [id=rtbassoc-05ad72d7a0531ee28]
module.network.aws_route_table_association.public1: Creation complete after 1s [id=rtbassoc-0dcdc8c9a5e92d331]
module.network.aws_route_table_association.public2: Creation complete after 1s [id=rtbassoc-099a83c99f258c36f]

Error: error reading Route Table Association (rtbassoc-07d32038d3161359d): empty result

  with module.network.aws_route_table_association.private1,
  on network/baseNetwork.tf line 184, in resource "aws_route_table_association" "private1":
 184: resource "aws_route_table_association" "private1" {

Steps to Reproduce

This does not happen all the time. Only occasionally, always on a fresh deploy (all we are doing right now).

terraform apply

Important Factoids

There doesn't appear to be an adjustable timeout for aws_route_table_association

References

#0000

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

ialidzhikov · 2021-11-09T07:09:08Z

Seems to be similar to #21629

anGie44 · 2021-11-11T20:06:14Z

Hi all 👋 the PR #21710 has been merged to hopefully address this nondeterministic issue. any findings from those who upgrade to the new provider that will be out later today (v3.65.0) would be greatly appreciated!

ellisroll-b · 2021-11-11T20:29:56Z

Whoo-hoo! We deploy regularly and pull latest under 4.x, in a very busy account. Hard to prove a negative, but if we see anything worth reporting, will do!

Thanks!

cdancy · 2021-11-12T03:30:00Z

@anGie44 still seeing issue after using latest released version 3.65.0:

22:27:47          	            	Error: error reading Route Table Association (rtbassoc-0ba95894cbf58a21f): empty result
22:27:47          	            	
22:27:47          	            	  with module.vpc.aws_route_table_association.public[0],
22:27:47          	            	  on .terraform/modules/vpc/main.tf line 1204, in resource "aws_route_table_association" "public":
22:27:47          	            	1204: resource "aws_route_table_association" "public" {

out resources look like so:

terraform {
  required_providers {
    aws = {
      source = "hashicorp/aws"
      version = ">= 3.65.0"
    }
    null = {
      source = "hashicorp/null"
    }
    template = {
      source = "hashicorp/template"
    }
  }
  required_version = ">= 0.13.1"
}

resource "aws_vpc_endpoint" "dynamodb" {
  vpc_endpoint_type = "Gateway"
  vpc_id            = module.vpc.vpc_id
  service_name      = "com.amazonaws.${var.Region}.dynamodb"
  tags              = local.tags
  timeouts {
    create = "30m"
    update = "30m"
    delete = "30m"
  }
  policy            = <<POLICY
    {
      "Statement": [
          {
          "Action": "*",
          "Effect": "Allow",
          "Resource": "*",
          "Principal": "*"
          }
      ]
    }
    POLICY
}

resource "aws_vpc_endpoint_route_table_association" "dynamodb" {
  count           = length(module.vpc.private_route_table_ids)
  route_table_id  = module.vpc.private_route_table_ids[count.index]
  vpc_endpoint_id = aws_vpc_endpoint.dynamodb.id
}

anGie44 · 2021-11-12T18:04:16Z

😞 thanks for reporting back @cdancy ! out of curiosity, after terraform returns that error, if you use the aws cli to query for the route table by filtering by the association ID , does that return a result?

cdancy · 2021-11-12T18:12:00Z

@anGie44 no idea. We have a big automated pipeline where this seems to pop fairly consistently at this point. When I've been doing, we'll say "local development and testing", things seems to work fine but in our busier and bigger pipeline this is just failing over and over again.

ellisroll-b · 2021-11-15T22:44:23Z

Sadly, I must also report its still happening.
provider.terraform-provider-aws_v3.65.0_x5: 2021/11/15 17:28:06

Same output and path as I originally reported in this thread. I can provide the dumps again, but its the same. 2 route tables are created, one is external internet gateway, the other internal NAT Gateway. In TRACE level logs, it loops waiting for route table association, which comes back successfully. AWS lookup on the association shows it successful as well. But the provider says no deal, and reports:

2021-11-15T17:28:06.676-0500 [INFO] provider.terraform-provider-aws_v3.65.0_x5: 2021/11/15 17:28:06 [DEBUG] [aws-sdk-go] <?xml version="1.0" encoding="UTF-8"?> <DescribeRouteTablesResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/"> <requestId>5490ec52-a264-411a-93a2-af095a00d9ea</requestId> <routeTableSet/> </DescribeRouteTablesResponse>: timestamp=2021-11-15T17:28:06.675-0500 2021-11-15T17:28:06.677-0500 [TRACE] maybeTainted: module.network.aws_route_table_association.private2 encountered an error during creation, so it is now marked as tainted 2021-11-15T17:28:06.677-0500 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for module.network.aws_route_table_association.private2 2021-11-15T17:28:06.677-0500 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for module.network.aws_route_table_association.private2 2021-11-15T17:28:06.677-0500 [TRACE] evalApplyProvisioners: module.network.aws_route_table_association.private2 is tainted, so skipping provisioning 2021-11-15T17:28:06.677-0500 [TRACE] maybeTainted: module.network.aws_route_table_association.private2 was already tainted, so nothing to do 2021-11-15T17:28:06.677-0500 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for module.network.aws_route_table_association.private2 2021-11-15T17:28:06.677-0500 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for module.network.aws_route_table_association.private2 2021-11-15T17:28:06.678-0500 [TRACE] vertex "module.network.aws_route_table_association.private2": visit complete 2021-11-15T17:28:06.723-0500 [INFO] provider.terraform-provider-aws_v3.65.0_x5: 2021/11/15 17:28:06 [DEBUG] [aws-sdk-go] DEBUG: Response ec2/DescribeRouteTables Details:

and then:

`
Error: error reading Route Table Association (rtbassoc-0e5c9c911e6e8bec6): empty result

with module.network.aws_route_table_association.private2,
on network/baseNetwork.tf line 166, in resource "aws_route_table_association" "private2":
166: resource "aws_route_table_association" "private2"
`

cdancy · 2021-11-16T15:18:42Z

@anGie44 is there anything anyone, myself included, can do to move things forward here and/or try something else? This is a major blocker for us at the moment.

jmcshane · 2021-11-18T18:28:11Z

I just wanted to say that we've also experienced this issue intermittently in our CI pipelines. For a job that takes 25 minutes to run, an intermittent failure like this is very challenging. Is there anything I could do to help test?

rfink · 2021-11-23T20:03:01Z

Currently having this issue

cdancy · 2021-11-23T20:57:29Z

Who do I have to bribe with free coffee/lunch to get this worked on?!? Someone just give me a name and/or email and I'll make it happen.

…

________________________________ From: rfink ***@***.***> Sent: Tuesday, November 23, 2021 3:03 PM To: hashicorp/terraform-provider-aws ***@***.***> Cc: Dancy, Chris ***@***.***>; Mention ***@***.***> Subject: ExtMsg: Re: [hashicorp/terraform-provider-aws] RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS (Issue #21683) CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments. Currently having this issue — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#21683 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB4BXY22DZUTAZGTOZPVM53UNPXQBANCNFSM5HTIFX6A>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

ellisroll-b · 2021-12-03T20:54:50Z

FWIW - this timing/eventual consistency failure does happen a lot still.
Happy to help with the bribe noted above... :)

Eli-Meitner · 2022-01-24T11:18:27Z

FYI - I added dependencies to the associations, this then waits for the subnet and table to be created before doing the association and stop failing for me on "empty result"

ellisroll-b · 2022-01-24T13:31:48Z

`//-----------------------------------------------------------
//waitRouteTableElements is a delay mechanism as AWS is reporting
//a network element is complete, before its accessible (most often
//the private routeTable) - This waits for AWS to claim the
//elements in the list are "created", then waits 5mins more
//
//It is currently referenced as a dependency by the route table
//association objects
resource "time_sleep" "waitRouteTableElements" {
depends_on = [
aws_route_table.publicRouteTable,
aws_route.publicInternetGatewayRoute,
aws_route_table.privateRouteTable,
aws_route.privateNatGatewayRoute,
aws_subnet.publicSubNet1,
aws_subnet.publicSubNet2,
aws_subnet.privateSubNet1,
aws_subnet.privateSubNet2,
]
create_duration = "5m"
}

resource "aws_route_table_association" "public1" {
depends_on = [time_sleep.waitRouteTableElements]
subnet_id = aws_subnet.publicSubNet1.id
route_table_id = aws_route_table.publicRouteTable.id
}
`

Been doing that from the beginning, but it still fails - from a trace dump, the provider waits and sees the dependencies created, but still fails.

Eli-Meitner · 2022-01-24T13:34:50Z

I did not add it to the time_sleep resource but directly on association:

resource "aws_route_table_association" "private" {
  count = var.create_vpc && length(var.private_subnets) > 0 ? length(var.private_subnets) : 0

  subnet_id = element(aws_subnet.private[*].id, count.index)
  route_table_id = element(
    aws_route_table.private[*].id,
    var.single_nat_gateway ? 0 : count.index,
  )
  depends_on = [
    aws_subnet.private,
    aws_route_table.private
  ]
}

resource "aws_route_table_association" "outpost" {
  count = var.create_vpc && length(var.outpost_subnets) > 0 ? length(var.outpost_subnets) : 0

  subnet_id = element(aws_subnet.outpost[*].id, count.index)
  route_table_id = element(
    aws_route_table.private[*].id,
    var.single_nat_gateway ? 0 : count.index,
  )
  depends_on = [
    aws_subnet.outpost,
    aws_route_table.private
  ]
}

resource "aws_route_table_association" "database" {
  count = var.create_vpc && length(var.database_subnets) > 0 ? length(var.database_subnets) : 0

  subnet_id = element(aws_subnet.database[*].id, count.index)
  route_table_id = element(
    coalescelist(aws_route_table.database[*].id, aws_route_table.private[*].id),
    var.create_database_subnet_route_table ? var.single_nat_gateway || var.create_database_internet_gateway_route ? 0 : count.index : count.index,
  )
  depends_on = [
    aws_subnet.database,
    aws_route_table.database
  ]
}

resource "aws_route_table_association" "redshift" {
  count = var.create_vpc && length(var.redshift_subnets) > 0 && false == var.enable_public_redshift ? length(var.redshift_subnets) : 0

  subnet_id = element(aws_subnet.redshift[*].id, count.index)
  route_table_id = element(
    coalescelist(aws_route_table.redshift[*].id, aws_route_table.private[*].id),
    var.single_nat_gateway || var.create_redshift_subnet_route_table ? 0 : count.index,
  )
  depends_on = [
    aws_subnet.redshift,
    aws_route_table.redshift
  ]
}

resource "aws_route_table_association" "redshift_public" {
  count = var.create_vpc && length(var.redshift_subnets) > 0 && var.enable_public_redshift ? length(var.redshift_subnets) : 0

  subnet_id = element(aws_subnet.redshift[*].id, count.index)
  route_table_id = element(
    coalescelist(aws_route_table.redshift[*].id, aws_route_table.public[*].id),
    var.single_nat_gateway || var.create_redshift_subnet_route_table ? 0 : count.index,
  )
  depends_on = [
    aws_subnet.redshift,
    aws_route_table.redshift
  ]
}

resource "aws_route_table_association" "elasticache" {
  count = var.create_vpc && length(var.elasticache_subnets) > 0 ? length(var.elasticache_subnets) : 0

  subnet_id = element(aws_subnet.elasticache[*].id, count.index)
  route_table_id = element(
    coalescelist(
      aws_route_table.elasticache[*].id,
      aws_route_table.private[*].id,
    ),
    var.single_nat_gateway || var.create_elasticache_subnet_route_table ? 0 : count.index,
  )
  depends_on = [
    aws_subnet.elasticache,
    aws_route_table.private
  ]
}

resource "aws_route_table_association" "intra" {
  count = var.create_vpc && length(var.intra_subnets) > 0 ? length(var.intra_subnets) : 0

  subnet_id      = element(aws_subnet.intra[*].id, count.index)
  route_table_id = element(aws_route_table.intra[*].id, 0)
  depends_on = [
    aws_subnet.intra,
    aws_route_table.intra
  ]
}

resource "aws_route_table_association" "public" {
  count = var.create_vpc && length(var.public_subnets) > 0 ? length(var.public_subnets) : 0

  subnet_id      = element(aws_subnet.public[*].id, count.index)
  route_table_id = aws_route_table.public[0].id
  depends_on = [
    aws_subnet.public,
    aws_route_table.public
  ]
}```

ellisroll-b · 2022-02-03T22:35:06Z

This doesn't seem to be correct. Found in the 3.xx.xx and apparently fixed in a 4.xxx version. If the fix works, we can't know for an extended period, as moving to a 4.xx provider is a big deal on our end. I am seeking a fix in the 3.xx provider.

…

On Thu, Feb 3, 2022, 5:10 PM Kit Ewbank ***@***.***> wrote: Closed #21683 <#21683> via #22927 <#22927>. — Reply to this email directly, view it on GitHub <#21683 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AORZDSIT2LUFB6OSMIBUQO3UZL4PFANCNFSM5HTIFX6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: <hashicorp/terraform-provider-aws/issue/21683/issue_event/6005985982@ github.com>

github-actions · 2022-02-10T18:13:29Z

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

ellisroll-b · 2022-02-10T18:27:23Z

When will a 3.xx fix be made?

…

On Thu, Feb 10, 2022, 1:13 PM github-actions[bot] ***@***.***> wrote: This functionality has been released in v4.0.0 of the Terraform AWS Provider <https://github.com/hashicorp/terraform-provider-aws/blob/v4.0.0/CHANGELOG.md>. Please see the Terraform documentation on provider versioning <https://www.terraform.io/docs/configuration/providers.html#provider-versions> 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 <https://github.com/hashicorp/terraform-provider-aws/issues/new/choose> following the template. Thank you! — Reply to this email directly, view it on GitHub <#21683 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AORZDSOIQCOXSPJGOEOBG4TU2P55NANCNFSM5HTIFX6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

cdancy · 2022-02-11T20:08:38Z

This seems to be working for us but now we're seeing the below which feels like a similar or related type of issue:

[2022-02-11T19:54:26.983Z]         	            	               

[2022-02-11T19:54:26.983Z]         	            	               Error: error reading EC2 Network ACL Rule (nacl-3954984924): couldn't find resource

[2022-02-11T19:54:26.983Z]         	            	               

[2022-02-11T19:54:26.983Z]         	            	                 with module.vpc.aws_network_acl_rule.public_outbound[2],

[2022-02-11T19:54:26.983Z]         	            	                 on .terraform/modules/vpc/main.tf line 668, in resource "aws_network_acl_rule" "public_outbound":

[2022-02-11T19:54:26.983Z]         	            	                668: resource "aws_network_acl_rule" "public_outbound" {

github-actions · 2022-05-13T02:39:27Z

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 bot added needs-triage Waiting for first response or review from a maintainer. service/ec2 Issues and PRs that pertain to the ec2 service. labels Nov 8, 2021

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

anGie44 mentioned this issue Nov 10, 2021

service/ec2/find: update call toDescribeRouteTables with paginated method #21710

Merged

This was referenced Nov 12, 2021

resource/aws_route: route is not saved in the state when it fails to be available (in 2m) on creation #21032

Closed

How to: configure timeouts for vpc module on aws_default_route_table terraform-aws-modules/terraform-aws-vpc#708

Closed

thatderek mentioned this issue Feb 3, 2022

aws_ec2_route_table_association: use retry logic on newly created resource #22927

Merged

ewbankkit closed this as completed in #22927 Feb 3, 2022

github-actions bot added this to the v4.0.0 milestone Feb 3, 2022

cdancy mentioned this issue Feb 11, 2022

error reading EC2 Network ACL Rule #23142

Closed

github-actions bot locked as resolved and limited conversation to collaborators May 13, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS #21683

RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS #21683

ellisroll-b commented Nov 8, 2021 •

edited

Loading

ialidzhikov commented Nov 9, 2021

anGie44 commented Nov 11, 2021

ellisroll-b commented Nov 11, 2021

cdancy commented Nov 12, 2021 •

edited

Loading

anGie44 commented Nov 12, 2021

cdancy commented Nov 12, 2021

ellisroll-b commented Nov 15, 2021

cdancy commented Nov 16, 2021

jmcshane commented Nov 18, 2021

rfink commented Nov 23, 2021

cdancy commented Nov 23, 2021 via email

ellisroll-b commented Dec 3, 2021

Eli-Meitner commented Jan 24, 2022

ellisroll-b commented Jan 24, 2022

Eli-Meitner commented Jan 24, 2022

ellisroll-b commented Feb 3, 2022 via email

github-actions bot commented Feb 10, 2022

ellisroll-b commented Feb 10, 2022 via email

cdancy commented Feb 11, 2022

github-actions bot commented May 13, 2022

RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS #21683

RouteTable association reports empty result - and apply fails, but routetable is properly associated in AWS #21683

Comments

ellisroll-b commented Nov 8, 2021 • edited Loading

Community Note

Terraform CLI and Terraform AWS Provider Version

Affected Resource(s)

Terraform Configuration Files

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Important Factoids

References

ialidzhikov commented Nov 9, 2021

anGie44 commented Nov 11, 2021

ellisroll-b commented Nov 11, 2021

cdancy commented Nov 12, 2021 • edited Loading

anGie44 commented Nov 12, 2021

cdancy commented Nov 12, 2021

ellisroll-b commented Nov 15, 2021

cdancy commented Nov 16, 2021

jmcshane commented Nov 18, 2021

rfink commented Nov 23, 2021

cdancy commented Nov 23, 2021 via email

ellisroll-b commented Dec 3, 2021

Eli-Meitner commented Jan 24, 2022

ellisroll-b commented Jan 24, 2022

Eli-Meitner commented Jan 24, 2022

ellisroll-b commented Feb 3, 2022 via email

github-actions bot commented Feb 10, 2022

ellisroll-b commented Feb 10, 2022 via email

cdancy commented Feb 11, 2022

github-actions bot commented May 13, 2022

ellisroll-b commented Nov 8, 2021 •

edited

Loading

cdancy commented Nov 12, 2021 •

edited

Loading