`vsphere-iso`: multiple NICs; only one NIC with IP reachability

[hc-github-team-packer]

This issue was originally opened by @heitmanr in https://github.com/hashicorp/packer/issues/11409 and has been migrated to this repository. The original issue description is below.

---

Building a VM with two NICs mapped to their vSphere-Portgroups works just fine.

Description

In my Setup, only one Portgroup contains a DHCP-Server.

• the 2nd NIC doesn't get an IP-Address (by design)
• the 2nd Portgroup would be in an isolated IP-Range
  • so an SSH-Connection to n IP-Address at this 2nd-NIC wouldn't be possible anyway.

Right now, the whole build-process gets stuck, in "Waiting for IP" => I assume, the script looks to the "wrong" NIC [which doesn't get an IP] => or it wait's, until all NICs got an IP-Address

Use Case(s)

Any dual-homed Server connecting different "network security zones, perimeter networks, etc."

Potential configuration

I'd suggest the possibility, to flag one or more NICs as "management"-Interface usable for packer. //of course, defaulting to "true" would make sense to avoid changes to standard, single-homed setups.

  network_adapters {
    network_card = "vmxnet3"
    network      = "LAB.Management"
    management = true
  }
 network_adapters {
    network_card = "vmxnet3"
    network      = "isolated LAN without DHCPd"
   management = false
  }

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.