Packer: Build 'vsphere-iso' errored: error creating vm: folder '/datacenter/vm/' not found

[Klashblack]

The following error i get is because our Datacenter is in a folder
/WEST/DATACENTER/

Can we get a option or a way to add a folder if the datacenter is in a folder?

==> vsphere-iso: Creating VM...
Build 'vsphere-iso' errored: error creating vm: folder '/DATACENTER/vm/' not found

==> Some builds didn't complete successfully and had errors:
--> vsphere-iso: error creating vm: folder '/DATACENTER/vm/' not found

==> Builds finished but no artifacts were created.
{

"builders": [
{
"type": "vsphere-iso",
"vcenter_server": "vcenterserver,
"username": "{{user vsphere_username}}",
"password": "{{user vsphere_password}}",
"datacenter": "datacenter",
"cluster": "CLUSTER1",
"communicator": "winrm",
"winrm_username": "Administrator",
"winrm_password": "{{user admin_password}}",
"vm_name": "W2K19STDX64TEST",
"convert_to_template": "true",
"datastore": "datastore",
"cpus": "2",
"ram": "4096",
"network_card": "vmxnet3",
"disk_controller_type": "lsilogic-sas",
"CPU_hot_plug": true,
"RAM_hot_plug": true,
"disk_size": "51200",
"iso_paths": [
"[datastore] ISO - Windows Server/SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_English_DC_STD_MLF_X22-02970.ISO",
"[datastore] ISO - Windows Server/VMware-tools-windows-10.3.10-12406962.iso"
],
"floppy_files": [
"setup/autounattend.xml",
"setup/setup.ps1",
"setup/vmtools.cmd"
]
}
],
"provisioners": [
{
"type": "windows-update"
}
]

Packer version

1.5.4

[luis-garza]

Hi! we are facing the same issue with vsphere-clone builder, we also have the datacenter inside a folder.
Would be really nice if someone could plan a fix for it, as thisis totally blocking us to use Packer in our private cloud.

[RPitt]

I think this is a duplicate of #9328 Fix packer vsphere-iso builder folder path now closed.

[TmCTux]

I believe the current nighlty build has integrated this change, but it still doesn't seem to fix the issue (I've tested it this morning and it still doesn't find the nested datacenter). So even though this one does look duplicate I'd keep it open for now.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.