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
Hey @ryancurrah, sorry for the delay in responding to this.
This is actually a long-standing issue in all of TF, as we, much like the other issues you have linked, work off of the standard library's default resolver.
Unfortunately this is not an issue that we have an easy answer. We are tracking this in more detail in issues such as hashicorp/terraform#3536. Once a better answer is available, I would imagine we will be implementing it across the entire provider ecosystem.
For more updates, I'd follow the referenced issue - there is also more detail in there as to what some people in the community are doing to mitigate the problem.
Attaching vSphere tags to virtual machines fails intermittently when deploying more than one virtual machine at the same time
Terraform Version
0.10.8
vSphere Provider Version
1.3.0
Affected Resource(s)
Please list the resources as a list, for example:
vsphere_virtual_machine
Terraform Configuration Files
Variables.tfvars file
Variables.tf
Main.tf file
Debug Output
Four virtual machines were spun up with this tf apply, 1 failed to get the tags applied and caused terraform to halt
terraform-vsphere-tag-debug.log
Expected Behavior
vSphere tags should have been attached to the virtual machine succesfully
Actual Behavior
HTTP call to attach the vSphere tag fails on a virtual machine and halts the terraform apply
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
linux_nodes
variableterraform apply
Repeat until failure occurs
Important Factoids
References
Below are similar issues encountered by other golang users
The text was updated successfully, but these errors were encountered: