Attempting to destroy a security group that can't be destroyed due to being attached to an instance, hangs instead of returns an error message

[paulcdejean]

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.11.7
• provider.aws v1.19.0
• provider.null v1.0.0

Affected Resource(s)

• aws_security_group

Expected Behavior

Terraform should have reported that it can't delete the security group because it's currently used by an instance. This is the behavior if you try and delete a security group via console.

Actual Behavior

Terraform got stuck on attempting to delete the security group.

Steps to Reproduce

Create a security group via terraform. Attach the security group to an instance that's not in terraform. Attempt to destroy the security group via terraform.

[fonglh]

This also happens if the security group is attached to an instance that IS in terraform, then a change that forces a new resource (e.g. security group description change) is made.

[sidewaiise]

Looks like the resource graph doesn't account for attached resources when destroying a security group. I've had to manually decomission the resources that the SG is attached to first, then run the terraform apply again.

Is there not something we can add like depends_on = ... to the resources to update the order in which resources get destroyed?

[carlosjgp]

this issue has been happening since 2016
hashicorp/terraform#8772

Is there a reason why this is not addressed or is just a matter of time?

I just spent 4 hours trying to find out if I had to manage the ELB ENIs on Terraform too :(

[paulcdejean]

I acknowledge that this is a dupe of #265

[ghost]

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!