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

Terraform destroy bug on aws_internet_gateway resource #3747

Closed
bensojona opened this issue Nov 4, 2015 · 4 comments
Closed

Terraform destroy bug on aws_internet_gateway resource #3747

bensojona opened this issue Nov 4, 2015 · 4 comments

Comments

@bensojona
Copy link
Contributor

I get the following error every time I terraform destroy my infrastructure.

Error applying plan:

4 error(s) occurred:

* aws_internet_gateway.public: Error waiting for internet gateway (igw-81138de4) to detach: couldn't find resource
* aws_subnet.private.1: Error deleting subnet: timeout while waiting for state to become 'destroyed'
* aws_subnet.private.2: Error deleting subnet: timeout while waiting for state to become 'destroyed'
* aws_subnet.private.0: Error deleting subnet: timeout while waiting for state to become 'destroyed'

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Full destroy output here.

@shanielh
Copy link
Contributor

shanielh commented Nov 4, 2015

Happens to me too, When I run terraform destroy again, It succeeds.

@phinze
Copy link
Contributor

phinze commented Nov 4, 2015

Yeah I've seen that as well. We probably need to treat that "couldn't find resource" error as a successful outcome.

If anybody has a small config that reproduces this issue, that would be helpful!

@catsby
Copy link
Contributor

catsby commented Apr 27, 2017

Closing this for now, let us know if anyone has a config that reproduces this today. Thanks!

@ghost
Copy link

ghost commented Apr 13, 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 13, 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