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"
Which results in this error (with the datastore names replaced with TestDatastoreX), even though the Datastore clearly exists. It worked fine prior to vSphere 5.0 and vCenter 5.0. Any ideas?
Note that all "possible completions" specified below work fine! Those that I have tried that are "not" in the possible completions do "not" work.
Error: Invalid target datastore specified (TestDatastore): Possible completions:
TestDatastore1
TestDatastore2
TestDatastore3
TestDatastore4
TestDatastore5
TestDatastore6
TestDatastore7
TestDatastore8
TestDatastore9
TestDatastore10
TestDatastore11
TestDatastore12
TestDatastore13
TestDatastore14
TestDatastore15
TestDatastore16
TestDatastore17
TestDatastore18
TestDatastore19
TestDatastore20
TestDatastore21
TestDatastore22
TestDatastore23
TestDatastore24
TestDatastore25
TestDatastore26
TestDatastore27
TestDatastore28
TestDatastore29
TestDatastore30
TestDatastore31
TestDatastore32
TestDatastore33
TestDatastore34
TestDatastore35
Completed with errors