Destroying a Target Group fails due to dependency issue

[random930]

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 Version

Affected Resource(s)

• aws_lb_target_group

Terraform Configuration Files

resource "aws_lb_target_group" "main" {
	name = "streamdelayer-lb-tg"
	port = 80
	protocol = "TCP"
	vpc_id = aws_vpc.external.id

	target_type = "ip"

	depends_on = [aws_lb.main]

	health_check {
		interval = 10
		port = 8000
		protocol = "tcp"
	}
}

resource "aws_lb_listener" "main" {
	load_balancer_arn = aws_lb.main.arn
	port = "80"
	protocol = "TCP"

	default_action {
		type = "forward"
		target_group_arn = aws_lb_target_group.main.arn
	}

	depends_on = [aws_lb_target_group.main]
}

Expected Behavior

If I make a change to the target_group in the TF file and run a normal "terraform apply", it should have destroyed the listener before the target_group, then rebuilt both, to avoid the error I experirenced.

Actual Behavior

I made a change to a target_group and ran "terraform apply". I got this in return:

aws_lb_target_group.main: Destroying... [id=arn:aws:elasticloadbalancing:us-east-2:473085186055:targetgroup/streamdelayer-lb-tg/7c9ead1bdaea9467]

Error: Error deleting Target Group: ResourceInUse: Target group 'arn:aws:elasticloadbalancing:us-east-2:473085186055:targetgroup/streamdelayer-lb-tg/7c9ead1bdaea9467' is currently in use by a listener or a rule
	status code: 400, request id: 5e7362db-f60c-426f-820c-dbe9c861c8a5

(It didn't try to destroy the listener for some reason, even when I added depends-on, which I didn't have originally)

Then, I tried destroying the same resource specifically: "terraform destroy -target=aws_lb_target_group.main"

And that worked:

aws_lb_listener.main: Destroying... [id=arn:aws:elasticloadbalancing:us-east-2:473085186055:listener/net/streamdelayer-lb/baf23672a324cb16/938699982d1aae65]
aws_lb_listener.main: Destruction complete after 1s
aws_lb_target_group.main: Destroying... [id=arn:aws:elasticloadbalancing:us-east-2:473085186055:targetgroup/streamdelayer-lb-tg/7c9ead1bdaea9467]
aws_lb_target_group.main: Destruction complete after 0s

Steps to Reproduce

See above

[sworisbreathing]

@random930 this looks to be the same issue as #5699

[random930]

Yes, except it reproduces with an updated version

…

On Mon, May 25, 2020, 4:51 PM Steven Swor ***@***.***> wrote: @random930 <https://github.com/random930> this looks to be the same issue as #5699 <#5699> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13294 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL3ATNCVFZO2OGO54XL3ODRTL76ZANCNFSM4M7IRTKQ> .

[acdha]

I hit this recently with 0.13 and it's a little worse than it was in #5699, #636, etc. There's no way to solve this using name because the listener update will be blocked waiting for the previous target group to delete, and that will also fail to trigger updates to any target group attachments you have. Using name_prefix works but then you're stuck with the inability to have a name longer than 6 characters.

[justinretzolk]

Hey @random930 👋 Thank you for taking the time to submit this issue. Given that there's been a few Terraform and AWS Provider releases since you initially filed it, can you confirm whether you're still running into this?

[MAXxATTAXx]

I can confirm this is happening on terraform v1.0.5 and v1.07

[jobwat]

Still an issue

I can't get terraform to destroy the aws_lb_listener_rule which is blocking the destroy of aws_lb_target_group

Error: error deleting Target Group: ResourceInUse: Target group 'xx' is currently in use by a listener or a rule

Terraform v1.1.4
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.72.0

[matmalone]

In my situation the least bad work-around I could figure out is tainting the associated aws_lb_listener before running apply.

[a0s]

Any news on that?
I had to move to name_prefix and now it looks disgusting, like a old_na485638753658376438.
It also takes downtime to make such a transition.