-
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_autoscaling_group] Attaching/Detaching a lot of loadbalancers fails #256
Comments
Is there any workaround for this issue? :) |
+1 |
This still exists in 2.17.0 |
… by 10 to prevent API and rate limiting errors Reference: #256 Reference: #10435 Reference: https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_AttachLoadBalancers.html Reference: https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_DetachLoadBalancers.html This change is complementary to the target group batching. The AutoScaling API for `AttachLoadBalancers` and `DetachLoadBalancers` only allow 10 elements at a time. In addition to the batching to split the API requests, we must wait for the batch to fully complete before moving onto the next batch, otherwise the API returns a rate limiting error: ``` --- FAIL: TestAccAWSAutoScalingGroup_LoadBalancers (360.22s) testing.go:569: Step 2 error: errors during apply: Error: Error updating Load Balancers for AutoScaling Group (tf-asg-2019101000090127270000000d), error: ValidationError: Trying to update too many Load Balancers/Target Groups at once. The limit is 10 ``` Output from acceptance testing: ``` --- PASS: TestAccAWSAutoScalingGroup_LoadBalancers (443.84s) ```
The fix to batch large |
This has been released in version 2.32.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
Just to followup here, the similar change to |
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! |
This issue was originally opened by @freeman as hashicorp/terraform#8718. It was migrated here as part of the provider split. The original body of the issue is below.
Hello,
We heavily use modules in our terraform stacks.
When updating some core modules this resulted in massive updates to the load balancers attached to some of our autoscaling groups and we are getting this error:
Terraform Version
Using terraform v0.7.3
Affected Resource(s)
Expected Behavior
The update should have succeded
Actual Behavior
We got the error mentionned earlier
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
From looking at the source this happens here
According to Auto Scaling Limits this will also be an issue with target groups.
I guess the feature request is for terraform to proceed in batches of 10 modifications at a time.
The text was updated successfully, but these errors were encountered: