You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating several servers from snapshots, the provider sometimes waits an additional minute in the "Still creating..." state despite the server being ready for a while.
# Omitted
hcloud_server.arm_small[2]: Creation complete after 1m9s [id=50992996]
hcloud_server.arm_small[0]: Creation complete after 1m9s [id=50992998]
hcloud_server.arm_small[1]: Creation complete after 1m10s [id=50992999]
hcloud_server.arm_small[4]: Still creating... [1m10s elapsed]
hcloud_server.arm_small[3]: Still creating... [1m10s elapsed]
# The servers are ready soon after this message# Omitted
hcloud_server.arm_small[4]: Creation complete after 2m11s [id=50992997]
hcloud_server.arm_small[3]: Creation complete after 2m11s [id=50993000]
What did you expect to happen?
The creation should be marked as complete as soon as possible (without exceeding the API rate limit).
The API client currently uses an exponential backoff while waiting for actions. The version in the provider does not use a max time, so it can get to a point where there are minutes between each check.
We have added an alternative "truncated" backoff in a recent version of hcloud-go: hetznercloud/hcloud-go#459
Unfortunately the hcloud-go in the terraform provider is stuck on the v1 branch (see #877).
For now you can switch to a constant backoff by modifying your provider:
provider"hcloud" {
token=var.hcloud_tokenpoll_function="constant"poll_interval="5s"# default is 500ms, which might cause rate-limit issues with the constant polling
}
What happened?
When creating several servers from snapshots, the provider sometimes waits an additional minute in the "Still creating..." state despite the server being ready for a while.
What did you expect to happen?
The creation should be marked as complete as soon as possible (without exceeding the API rate limit).
Please provide a minimal working example
var.image_id_arm
is the image id of my snapshot. The snapshot was made in NBG1 and is 350MB. It is made with the following packer file:The text was updated successfully, but these errors were encountered: