Terraform will wait until nodepool is crated, then continue execution.
Actual Behavior
Terraform throws a timeout error if creation takes more than 20 minutes. Pool is eventually created but terraform execution is halted on the error, leaving behind a terraform state out of sync with the created resources.
Steps to Reproduce
terraform apply
Workaround
Can be worked around by declaring specific timeouts in the resource specification:
OVH will very often not spin up nodes within the default 20 minute timeout. While default timeout can be overridden, I suggest increasing the default timeout to reflect a realistic range of creation times. This will remove the need for adding an override, and reduce friction for new users.
Describe the bug
create nodepool will often fail due to timeout.
Terraform Version
N/A
OVH Terraform Provider Version
ovh/ovh v0.42.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Terraform will wait until nodepool is crated, then continue execution.
Actual Behavior
Terraform throws a timeout error if creation takes more than 20 minutes. Pool is eventually created but terraform execution is halted on the error, leaving behind a terraform state out of sync with the created resources.
Steps to Reproduce
terraform apply
Workaround
Can be worked around by declaring specific timeouts in the resource specification:
Additional context
OVH will very often not spin up nodes within the default 20 minute timeout. While default timeout can be overridden, I suggest increasing the default timeout to reflect a realistic range of creation times. This will remove the need for adding an override, and reduce friction for new users.