OVF Tool Failing to Execute Upload

[barnette08]

When trying to execute a conversion and upload directly to vCD, I get the following error after authenticating and connecting to the vCD URL:

Error: Multiple networks found on target. Possible completions are:

Org-Network 1

Org-Network 2

I've been using the format of ovftool [OVA-FILE] [VCLOUD-LOCATOR] per the documentation, but it seems to be looking a network and all I need to do is upload it to the catalog.  The blog post below mentions I should be able to just get the -vCloudTemplate flag to true, but that doesn't seem to work either.

Here is the syntax I am using:

c:\sourcepath\source.ova "vcloud://username:password@vcloudURL:443?org=orgName&vappTemplate=OVF_Test&catalog=Catalog&vdc=orgVDC"

VMware Blog on Topic

https://blogs.vmware.com/vsphere/2013/05/how-to-import-an-ova-into-vcloud-director.html

OVF Tool 3.5.0

vCloud 5.1.2

[Chrigoli]

Hi barnette08

I suppose you have at least one NIC in your VM in the ova. So if you have one NIC, the ovftool tries to map the network of the NIC to a network existing in vCD. In this case, in vCD you have the two networks Org-Network1 and 2.

You can try to map the networks by adding the following parameter to your syntax:

--net:sourceNet=targetNet     (where soureNet is the currently existing network to which the NIC in the ova is connected, and targetNet is the Org-Network1 or 2 within vCD)

We had a lot of VMs with NICs connected and now imported the VMX files instead of OVF. In this way we were able to first remove all the NICs within the VMX file (just removing the lines which contain Ethernet*.*) and then import to vCD with the ovftool without the need to select a target Network.

Hope this helps.

Chrigoli

[barnette08]

Chrigoli,

This helps.  My big curiosity is that why is the tool checking for a NIC if I am publishing it to the catalog though?  I don't think it should be checking NIC information in the VMX file unless I am deploying it into the cloud?

I also need help with the --vCloudTemplate switch and where it should be in my syntax, maybe that will negate the need for the NIC information?

[Chrigoli]

Well because the NIC information and the network it is connected to are saved if you add a vApp to the catalog. This is in my opinion the intended use, that if you deploy a vApp from Catalog, that the included VMs already have the NICs and the network connection. Otherwise you would have to add a NIC manually for each deployed VM.

Btw. we deployed the imported VMs first, made Windows Updates, VM Tool Updates, NIC configuration, etc. and then added manually to the Catalog. Maybe this would be the best way for you too.

And we removed all the Org Networks except of one to get rid of the Network selection issue with the ovf tool (we have a dedicated LIBRARY Org containing all the templates and catalogs).

The syntax should look like this:

ovftool <options> <source locator> <target locator>

so in your case including the vCloud Template switch:

ovftool --vCloudTemplate "c:\sourcepath\source.ova" "vcloud://username:password@vcloudURL:443?org=orgName&vappTemplate=OVF_Test&catalog=Catalog&vdc=orgVDC"

Check out the OVF Tool Guide (page 20ff) for additional options: http://www.vmware.com/support/developer/ovf/ovf301/ovftool-301-userguide.pdf

For us the --diskMode=thin was important as well (to create the disks Thin Provisioned instead of Thick)