Fixed DefaultWaitTimeoutForHCPControlPlaneInMinutes and timeouts while still installing

[chrisahl]

We are attempting to do a bulk create of 20 ROSA clusters at a time in the same AWS account and region. It appears that there is some throttling of 13 ROSA creates at a time, so it takes until one of these 13 complete until any additional ROSA deploys start running. This is leading to us seeing timeouts.

Is there a dynamic way to change the hard coded value of:

terraform-provider-rhcs/provider/clusterrosa/common/consts.go

Line 18 in 58b45a1

DefaultWaitTimeoutForHCPControlPlaneInMinutes = int64(20)

?

Any reason for the 20 min vs something larger? Any other suggestions for achieving higher success rates?

Thanks.

[willgarcia]

Hi @chrisahl

I am a user of this provider and suspect having the same issue when deploying clusters in bulk.

My clusters show in ready state but Terraform fails with the following error: "Waiting for cluster creation finished with the error".

Is that the error you see?

According to the different places in code showing this message, the actual error should be added at the end of the error message but that does not seem to be the case for me. I would like to confirm it is timeout related.

At TF re-run, the clusters get deleted as well because of the TF state erroring, so it takes a long time to get lucky.

[chrisahl]

@willgarcia In my case I get an error saying the error is "installing" because it is timing out. I think it would be good if DefaultWaitTimeoutForHCPControlPlanInMinutes was parameterized similar to how DefaultWaitTimeoutInMinutes has the ability to use
resource "rhcs_cluster_wait" "rosa_cluster" {
cluster = rhcs_cluster_rosa_classic.rosa_sts_cluster.id

timeout in minutes

timeout = 60
}

because different AWS regions take longer than others to provision based on your geo location and time of day/load.

[chrisahl]

https://issues.redhat.com/browse/OCM-12006 was recently opened and may help get this addressed