Skip to content
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

servicecatalog: Default waiter timeouts of 3 minutes are not long enough to provision a product #20253

Closed
jcmcken opened this issue Jul 20, 2021 · 2 comments · Fixed by #20254
Assignees
Labels
service/servicecatalog Issues and PRs that pertain to the servicecatalog service.
Milestone

Comments

@jcmcken
Copy link

jcmcken commented Jul 20, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.15.4
on linux_amd64

  • provider registry.terraform.io/hashicorp/aws v3.47.0

Affected Resource(s)

  • aws_servicecatalog_provisioned_product

Terraform Configuration Files

We aren't able to share these configuration files at present, but they're pretty standard. We have a Service Catalog product that provisions an AWS account using AWS Control Tower-generated CloudFormation. This provisioning takes longer than 3 minutes (and in general, CloudFormation templates can conceivably be expected to take longer depending on how many resources are being provisioned)

Debug Output

Panic Output

N/A

Expected Behavior

Terraform waits for the product to be fully provisioned before timing out.

Actual Behavior

Terraform times out after 3 minutes. This value of 3 minutes is hardcoded and seemingly unconfigurable.

When you run Terraform again, it will claim the resource is tainted, requiring manual effort to resolve.

Output looks like:

Error: error describing Service Catalog Provisioned Product (pp-xxxxxxxxxxxx): timeout while waiting for state to become 'AVAILABLE' (last state: 'UNDER CHANGE', timeout: 3m0s)

Steps to Reproduce

  1. terraform apply

Important Factoids

We're using AWS Control Tower with Service Catalog. It should not be much different from provisioning regular CloudFormation, but it's worth mentioning our use case.

References

N/A

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/servicecatalog Issues and PRs that pertain to the servicecatalog service. labels Jul 20, 2021
@YakDriver YakDriver removed the needs-triage Waiting for first response or review from a maintainer. label Jul 20, 2021
@YakDriver YakDriver self-assigned this Jul 20, 2021
@github-actions github-actions bot added this to the v3.51.0 milestone Jul 21, 2021
@github-actions
Copy link

This functionality has been released in v3.51.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!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/servicecatalog Issues and PRs that pertain to the servicecatalog service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants