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 waiting for route table (rtb-xxxxxx) to become destroyed: timeout while waiting for state to become '' #8539

Closed
brikis98 opened this issue Aug 29, 2016 · 2 comments

Comments

@brikis98
Copy link
Contributor

brikis98 commented Aug 29, 2016

Terraform Version

Terraform v0.7.2

Affected Resource(s)

  • aws_route_table

Terraform Configuration Files

I have a set of templates that create a VPC, route tables, subnets, and so on. I get an error for a route table I created for a public subnet:

resource "aws_route_table" "public" {
    vpc_id = "${aws_vpc.main.id}"
    tags {
        Name = "${var.vpc_name}-public"
    }
}

Expected Behavior

When I run terraform destroy, all the resources, including that route table, get deleted.

Actual Behavior

Intermittently, when I run terraform destroy, I get the following error:

* aws_route_table.public: Error waiting for route table (rtb-796fcb1f) to become destroyed: timeout while waiting for state to become ''

If I run terraform destroy a second time, the error goes away.

Steps to Reproduce

  1. terraform apply
  2. terraform destroy

Important Factoids

I don't remember seeing this error before Terraform 0.7, so perhaps some recent change has broken the destroy logic?

@pawelprazak
Copy link

pawelprazak commented Oct 7, 2016

Got the same error on apply with Terraform v0.7.4

* aws_route_table.identity-management-private-routing-table: Error waiting for route table (rtb-xxxxxxx) to become available: timeout while waiting for state to become 'ready' (timeout: 2m0s)

@ghost
Copy link

ghost commented Apr 10, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants