-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
AWS ALB http/https listener creation/destruction unstable and caused errors for dependencies #16779
Comments
This issue has been automatically migrated to hashicorp/terraform-provider-aws#2456 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know. |
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. |
Hi there,
Recently we've found out the creation/destruction of our ALB http/https (especially https one) listener become very unstable, it's very common (but not reproducible every time) that it failed the first time (with error described below) - the symptom is like the
aws_alb_listener
resource is created but ARN is not recorded in state - that caused failure for dependent resources likeaws_alb_listener_rule
, or it's destroyed duringterraform destroy
but is somehow not completely gone soaws_alb_target_group
deletion failed (as target group is in-use by the listener).We don't get these errors every time but it's increasingly happening recently and a small test with just few resources regarding ALB and running several
apply
anddestroy
continuously (liketerraform destroy -force && terraform apply && terraform destroy -force && terraform apply
) would occasionally produce such errors (with our real production code which is much more complex the errors happened more often):here is the TF configuration for test
Apply Error
In this case actually the Listener is already created in AWS.
Destroy Error (after a successful apply)
And in this case when I try delete the target group from EC2 Console there's no issue (as the listener is actually deleted).
Terraform version is 0.10.7
The text was updated successfully, but these errors were encountered: