-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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_lb_listener read taking longer than 1 minute timeout #8025
Comments
Hi @b-dean thanks for opening up this issue, and I'm sorry to hear that you are running into trouble. I appreciate you highlighting the references here. If I understand your description correctly you can only, sometimes, reproduce when trying to run plan multiple times in parallel, correct? If so, do you exhibit this issue with different Terraform configurations that you may have? Possibly indicating an external request issue. If you enable debug logging at the time of running plan and/or apply you should be able to get some information on what error is being thrown before hitting the 1 minute timeout. TF_LOG=debug TF_LOG_PATH=log.txt terraform plan |
This potentially relates to #7873 if it is being caused by rate limiting/throttling. The |
@nywilken, it's the same configuration files but different terraform workspaces, in parallel. So the difference in the I can get some debug logs although since it doesn't always happen, it might be a few days before I find anything. |
@bflad thanks for calling this out. This is the first thing that came to mind for me as well. But want to see if there was anything in the logs that would suggest otherwise. |
This is happening to me as well, in only one alb, with multiple listeners and many listener rules. |
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! |
Community Note
Description
I regularly have
terraform plan
fail because it can't refresh anaws_lb_listener
in a minute. I don't know if this matters but we have a lot of listeners on our account, 16 ALBs, 21 NLBs, and 90 ELB classic (not sure if that affects these sort of describes or not).When I run
it almost always completes in less than a second. And most of our
terraform plan
runs work too, but sometimes it doesn't and gets this error.It'd be nice to have some way to make this longer than a minute
Terraform Version
terraform 0.11.11
aws provider 1.60.0
Affected Resource(s)
Terraform Configuration Files
Nothing special, this is from the example from the aws_lb_listener docs. I'm not sure that anything in the configuration is causing the problems.
Expected Behavior
terraform plan
orterraform refresh
can run without timing outActual Behavior
Steps to Reproduce
terraform plan
Important Factoids
When we are running our
terraform plan
we are often running multiple terraform plans, for different workspaces (from different working directories), in parallel. I don't know if the combination of so many describe-listeners requests happening at once is the problem, but it's very difficult to reproduce.References
The line of code in question in the
aws_lb_listener
resource:https://github.com/terraform-providers/terraform-provider-aws/blob/v1.60.0/aws/resource_aws_lb_listener.go#L517
The text was updated successfully, but these errors were encountered: