Error: No network mapping specified. OVF networks: bridged. Target networks:

[gudipudipradeep]

` Code: network_interfaces { virtual_network = "${var.virtual_network}" # Required for each network interface, Specify the Virtual Network name. } Plan Command

• resource "esxi_guest" "K8SMaster" {

  • boot_disk_size = (known after apply)

  • disk_store = "data2"

  • guest_name = "check-Linux-Master"

  • guest_shutdown_timeout = (known after apply)

  • guest_startup_timeout = 600

  • guestinfo = {

    • "userdata" = "XYZ="
    • "userdata.encoding" = "gzip+base64" }

  • guestos = (known after apply)

  • id = (known after apply)

  • ip_address = (known after apply)

  • memsize = "8192"

  • notes = (known after apply)

  • numvcpus = "2"

  • ovf_source = "/mnt/SPS-Linux-Nodexx/SPS-Linux-Nodexx/SPS-Linux-Nodexx.vmx"

  • power = "on"

  • resource_pool_name = (known after apply)

  • virthwver = (known after apply)

  • network_interfaces {

    • mac_address = (known after apply)
    • nic_type = (known after apply)
    • virtual_network = "ML Subnet .61" } } `

` Apply command showing following issue Getting issue with Error: There was an ovftool Error: Opening VMX source: /mnt/SPS-Linux-Nodexx/SPS-Linux-Nodexx/SPS-Linux-Nodexx.vmx Opening VI target: vi://UserName@hypervisor.test.fileraft.com:443/ Error: No network mapping specified. OVF networks: bridged. Target networks: ML Subnet .61 VM Network Completed with errors

 pid-25682-guest_functions.go:24: [guestGetVMID] result:
2019-09-27T13:24:15.279-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: pid-25682-guest-create.go:249: **[guestCREATE] ovf_cmd: ovftool --acceptAllEulas --noSSLVerify --X:useMacNaming=false -dm=thin --name='check-Linux-Master' --overwrite -ds='data2'  '/mnt/SPS-Linux-Nodexx/SPS-Linux-Nodexx/SPS-Linux-Nodexx.vmx' 'vi://UserName:Password@hypervisor.test.fileraft.com/'**
2019-09-27T13:24:16.069-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: pid-25682-guest-create.go:253: [guestCREATE] ovftool output: "Opening VMX source: /mnt/SPS-Linux-Nodexx/SPS-Linux-Nodexx/SPS-Linux-Nodexx.vmx\nOpening VI target: vi://UserName@hypervisor.test.fileraft.com:443/\nError: No network mapping specified. OVF networks:   bridged. Target networks:   ML Subnet .61  VM Network\nCompleted with errors\n"
2019-09-27T13:24:16.069-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: pid-25682-guest-create.go:256: Failed, There was an ovftool Error: Opening VMX source: /mnt/SPS-Linux-Nodexx/SPS-Linux-Nodexx/SPS-Linux-Nodexx.vmx
2019-09-27T13:24:16.069-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: Opening VI target: vi://UserName@hypervisor.test.fileraft.com:443/
2019-09-27T13:24:16.069-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: Error: No network mapping specified. OVF networks:   bridged. Target networks:   ML Subnet .61  VM Network
2019-09-27T13:24:16.069-0700 [DEBUG] plugin.terraform-provider-esxi_v1.5.0: Completed with errors

` I think network switch is missing --network="ML Subnet .61" from command line. Please can you help on this issue.

[gudipudipradeep]

` SPS-Linux-Nodexx.vmx .vmx is missing from following source code i think and virtual_networks[0][0] might be a problem

if (strings.HasSuffix(src_path, ".ova") || strings.HasSuffix(src_path, ".ovf")) && virtual_networks[0][0] != "" { net_param = " --network='" + virtual_networks[0][0] + "'" } ` is this condition is really required (strings.HasSuffix(src_path, ".ova") || strings.HasSuffix(src_path, ".ovf")) i think this alone fine virtual_networks[0][0] != ""

[josenk]

If you take a look at the ovftool manual, the --network option is for ova/ovf only...

Also, you might be able to do mapping using vmx files, but it gets complex when the number of network interfaces on the source doesn't match the requirement on the destination. For example, how would you handle 4 network interfaces configured in the source VMX file, but you want to use only one nic on the destination? There is no way to map many to none, or none to many....

I found the best way to use local VMX source files is to strip out all the "network" configuration from the vmx file. The plugin will happily add whatever is needed. I'll update the README to better clarify local source VMX files should not have any networks configured.

[josenk]

I updated the "Known Issues" section...

• Using a local source vmx files should not have any networks configured. There is very limited network interface mapping abilities in ovf_tools for vmx files. It's best to simply clean out all network information from your vmx file. The plugin will add network configuration to the destination vm guest as required.