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 more than one VMs with Terraform (either rc1, rc2 or rc4), I always get timeout before it can finish the last VMs I want to deploy while getting an
I even went into the Proxmox event manager (the perl5 config files) to extend the custom timeout period, but to no avail.
It can happen with 1 VM and I get timed out after 2 minutes (and sometimes not), but it happen more often with deployment of 4 to 10 VMs. Then... something odd happens. When I want to deploy 4 or 5 VM in one deployment file, it will fail at the 4th or 5th. But when I want to deploy 9, it will fail at the 8th or 9th. It's a bit weird.
Has anyone been confronted with the same problem and found a solution/fix, or is it a bug to be fixed ?
The text was updated successfully, but these errors were encountered:
When creating more than one VMs with Terraform (either rc1, rc2 or rc4), I always get timeout before it can finish the last VMs I want to deploy while getting an
Here is an example of the error I get :
Error: error updating VM: 596 Connection timed out, error status: (params: map[agent:1 balloon:0 bios:seabios cicustom: cipassword: ciupgrade:1 cores:2 cpu:host delete:ide2,
I already added the required parameters to extend the timeout both in the provider section
And also inside the main.tf file :
I even went into the Proxmox event manager (the perl5 config files) to extend the custom timeout period, but to no avail.
It can happen with 1 VM and I get timed out after 2 minutes (and sometimes not), but it happen more often with deployment of 4 to 10 VMs. Then... something odd happens. When I want to deploy 4 or 5 VM in one deployment file, it will fail at the 4th or 5th. But when I want to deploy 9, it will fail at the 8th or 9th. It's a bit weird.
Has anyone been confronted with the same problem and found a solution/fix, or is it a bug to be fixed ?
The text was updated successfully, but these errors were encountered: