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
Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
Do not leave "+1" or other comments that do not add relevant information or questions.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Terraform
v1.7.5
Terraform Provider
vsphere v2.7.0 on windows_amd64
VMware vSphere
8.0.2
Description
When executing "ovf_deploy" on "vsphere_virtual_machine" under Windows 10 platform, the following error message appears.
Checking with vSphere Client, OVF has been successfully deployed, but the VM is not powered on.
│ Error: error while fetching the created vm, vm '\Datacenter\vm\nested\nested-esxi01' not found
│
│ with vsphere_virtual_machine.vmFromLocalOvf,
│ on main.tf line 56, in resource "vsphere_virtual_machine" "vmFromLocalOvf":
│ 56: resource "vsphere_virtual_machine" "vmFromLocalOvf" {
But, when the same code is executed on the Ubuntu 22.04 platform, no error is output, the OVF is deployed successfully and the VM powers on.
I think perhaps Pull request # 2118 is related to this issue.
When using the filepath library of the go language, /(slash) is used as the directory separator in the Linux platform, but (backslash) is used in the Windows platform.
This appears to be the cause of the "vm not found" returned from the virtualmachine.FromPath function.
When I replaced filepath to path and built, the problem did not occur.
Community Guidelines
Terraform
v1.7.5
Terraform Provider
vsphere v2.7.0 on windows_amd64
VMware vSphere
8.0.2
Description
When executing "ovf_deploy" on "vsphere_virtual_machine" under Windows 10 platform, the following error message appears.
Checking with vSphere Client, OVF has been successfully deployed, but the VM is not powered on.
But, when the same code is executed on the Ubuntu 22.04 platform, no error is output, the OVF is deployed successfully and the VM powers on.
I think perhaps Pull request # 2118 is related to this issue.
When using the filepath library of the go language, /(slash) is used as the directory separator in the Linux platform, but (backslash) is used in the Windows platform.
This appears to be the cause of the "vm not found" returned from the virtualmachine.FromPath function.
When I replaced filepath to path and built, the problem did not occur.
Affected Resources or Data Sources
resource/vsphere_virtual_machine
Terraform Configuration
Debug Output
https://gist.github.com/sshirata2/8ae04479866db6f8363c0d2e02fdddd2
Panic Output
No response
Expected Behavior
Ovf is deployed and the virtual machine is powered on.
Actual Behavior
Error was output and Apply failed.
Steps to Reproduce
terraform apply
Environment Details
Windwos 10 22H2
Screenshots
No response
References
#2118
The text was updated successfully, but these errors were encountered: