It appears that ovftool 3.0.1 has an issue while specifying the target datastore when importing an OVF when the VI is a vCenter 5.0 server with ESX 5.0 Update 1 hosts that have a large number of Datastores. The cluster where this problem occurs has 148 Datastores.
Some datastores work, most don't. This is a new problem since ovftool 2.0.1 worked fine when this cluster was at ESX 4.0 Update 3.
An example statement that will cause the problem (with all names replaced with "test" names):
"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --name="TestVM" --datastore="TestDatastore" --network=TestNetwork --vmFolder="TestFolder" http://192.168.0.1/public/ovfs/testvm.ovf vi://"username:password"@vcenter.test.com/"Data Center"/host/"HA and DRS"/Resources/"Test Resource Pool"
Hi Erick
We have found an issue with folders: When a datastore is in a folder, ovftool will not see it. If this is the case in your setup, we are aware of it and will fix it.
I am also facing the same issue. I specified the --ds correctly but no luck. Any help on this?
Unfortunately not yet... I have a ticket open with Vmware, though, so I'm hoping they can figure this out.
Eric
Still no luck with VMware's support. They are still looking at it, in theory, so I'll provide an update asap once they have a solution.
Eric
Hi Erick
We have found an issue with folders: When a datastore is in a folder, ovftool will not see it. If this is the case in your setup, we are aware of it and will fix it.
This error was bugging me for hours until i found this post. Moving the datastore out of the folder worked for me.
Thank you
Thank you!! This is indeed the problem and solved the issue for us (temporarily, since we need folders in our environment). Hopefully a fix will be issued soon.
Eric
What is the status of fixing this error, please?
I'd like to know too. Been waiting almost 7 months.
I think this is broken again in ovftool version 4. I am having the exact same issue. with ESXi 5.1 and ovftool 4. The only difference is that ovftool suggest the datastores to use but even those don't work.
There does seem to be an issue with the way ovftool parses its arguments.
For me, --datastore datastore1 did not work, but --datastore=datastore1 did work, regardless of whether your vmx file is in the current directory or not.
I will see about getting that fixed in the next release of ovftool.