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
[Bug]: aws_rds_cluster times out when creating servelessV2 cluster from snapshot #37154
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @jjpzt87 👋 Thank you for taking the time to raise this! Are you using Terraform Enterprise by chance? This looks a lot like Terraform Enterprise's default runner timeout. |
hey @justinretzolk! yes i am using TerraformCloud (TFC) for my backend, but the apply timeout is supposed to be 24h on TFC. I will try creating it locally and see if the timeout is from TFC or the resource. Thanks! |
hey @justinretzolk! you were right, the timeout was coming from TFC. running it locally worked and then i just imported. Thanks a lot |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Terraform Core Version
1.5.6
AWS Provider Version
4.45.0
Affected Resource(s)
aws_rds_cluster
Expected Behavior
i am setting timeouts values greater that 120m (default value), the creation should timeout when the new custom value is reached.
Actual Behavior
i am setting timeouts as:
The creation is timing out after 2h (120m default value)
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
base RDS:
Migration:
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: