import.ova always displays invalid value <Network> for element 'Connection'

[lamw]

Seeing a strange warning when deploying any OVA/OVF related to the VM defined network within the OVF. This is merely a label that the creator of an OVF maps to virtual interfaces and perhaps we might be assuming a particular name.

Here's an example of the error:

─[0] <> govc import.ova -options=vesxi3.json /Volumes/Storage/Images/nested_esxi_appliance_v6.0u2.ova
[02-04-16 07:41:43] Warning: Line 140: Invalid value 'VM Network' for element 'Connection'.
[02-04-16 07:41:43] Warning: Line 152: Invalid value 'VM Network' for element 'Connection'.
[02-04-16 07:41:57] Uploading Nested_ESXi6.x_Appliance_Template_v3-disk1.vmdk... OK
[02-04-16 07:41:57] Uploading Nested_ESXi6.x_Appliance_Template_v3-disk2.vmdk... OK
[02-04-16 07:41:57] Uploading Nested_ESXi6.x_Appliance_Template_v3-disk3.vmdk... OK
[02-04-16 07:41:57] Powering on VM...
[02-04-16 07:41:58] Injecting OVF environment...

Here's the OVA that I was using: https://bintray.com/artifact/download/photon-controller/esxi-appliances/nested_esxi_appliance_v6.0u2.ova

[cblomart]

Apparently OvfNetworkMapping is not used.
This should be used in OvfCreateImportSpecParams to create a mapping between ovf/a declared networks and configured networks (govc/importx/ovf.go line 209).

The question here is that there are multple networks declared in the ovf/a so, how to specify them on the command line? (simple csv and/or in a kind of file like options?)

[lamw]

@cblomart Given we have ability to parse the OVF and generate spec file using import.spec, I think my personal preference would be to have it in that same options file. ovftool today uses CLI options but for some OVF which may have more than one network, it could get messy on CLI. I actually like the simplicity of how govc handles imports via options files

[dougm]

Related: #460

[asifiqbal]

Yep I am having same issue...

$ govc import.ova --options=foo -dc="*OMH" -name=omh-nbsg-99 -ds=omh-vstorp1-01-02-lvshared01 src/Fortigate-VM64-v524-vmxnet3.ova
[15-04-16 19:33:25] Warning: Line 129: Invalid value 'OuterNBS' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 140: Invalid value 'InnerNBS' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 151: Invalid value 'InterNBS' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 162: Invalid value 'Outside-DMZ' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 173: Invalid value 'Inside-DMZ' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 184: Invalid value 'NBS-CustTest' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 195: Invalid value 'non-routing' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 206: Invalid value 'non-routing' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 217: Invalid value 'non-routing' for element 'Connection'.
[15-04-16 19:33:25] Warning: Line 228: Invalid value 'AppMgt' for element 'Connection'.
[15-04-16 19:33:32] Uploading foo-disk1.vmdk... OK
[15-04-16 19:33:32] Uploading foo-disk2.vmdk... OK

Would be nice if I could define the network adapters

[srbry]

Potential solution added to #460 using import.ova -options if anyone is still struggling with this

[avnish30jn]

I am already adding the network mapping, but still the warning comes.

[anfernee]

the warning comes from VC, as described here: http://pubs.vmware.com/vsphere-6-5/index.jsp#com.vmware.wssdk.apiref.doc/vim.OvfManager.CreateDescriptorResult.html

Close this issue, because govc as a client is doing what it should do.