-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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 Client VPN Resource Timeouts are too low #23787
Comments
Default timeout for `aws_ec2_client_vpn_route` is 1 minute for all operations. Trying to attach routes in `eu-central-1` for a peered VPC, it constantly fails with: ``` │ Error: error waiting for EC2 Client VPN Route (cvpn-endpoint-xxx,subnet-yyy,10.100.0.0/16) create: timeout while waiting for state to become 'active' (last state: 'creating', timeout: 1m0s) │ │ with module.ec2_client_vpn[0].aws_ec2_client_vpn_route.default[0], │ on .terraform/modules/ec2_client_vpn/main.tf line 242, in resource "aws_ec2_client_vpn_route" "default": │ 242: resource "aws_ec2_client_vpn_route" "default" { ``` and ``` │ Error: error waiting for EC2 Client VPN Route (cvpn-endpoint-xxx,subnet-yyy,10.100.0.0/16) delete: timeout while waiting for resource to be gone (last state: 'deleting', timeout: 1m0s) ``` With this commit, we increment the timeout to 5 minutes. In my experiments, the route is always available in around 90 seconds. 5 minutes gives us plenty of time, and still is not too long to wait in case of problems. Upstream issue: hashicorp/terraform-provider-aws#23787 I think fixing here is good, until we wait for an upstream improvement, because I am currently blocked
I created PR #30552 |
This functionality has been released in v4.63.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. Thank you! |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform: 1.1.7
AWS Provider Version: 4.5.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Resources would be created/deleted cleanly. Timeout needs to be raised on these resources to 2 minutes or more. This can be done in hcl, but the default should be increased.
Actual Behavior
The timeout on these resources is hard coded to 1m. In my tests, creating and destroying these resources can take anywhere from 50-75 seconds. So about half the time the transaction fails. Which results in tainted resources that have to be destroyed and created again. When you have a number of routes/auth rules, this basically can never complete successfully.
Steps to Reproduce
terraform apply
Important Factoids
Raising this value with the
timeouts
metadata block to 2m solved this issue for me.The text was updated successfully, but these errors were encountered: