rancher: vSphere node driver - VM deployed from content library is not setting network as per node template

What kind of request is this (question/bug/enhancement/feature request): Bug

Steps to reproduce (least amount of steps as possible):

• Create a vsphere node template with creation method as content library
• Create a cluster using the new template

Result:

• VM gets created with no network

Other details that may be helpful:

Rancher trace log shows that the network parameters are passed to rancher-machine via flag -vmwarevsphere-network

[TRACE] buildCommand args: [rancher-machine --debug create -d vmwarevsphere --engine-install-url https://releases.rancher.com/install-docker/19.03.sh --vmwarevsphere-cfgparam disk.enableUUID=TRUE --vmwarevsphere-datastore /NUCDC/datastore/DS01 --vmwarevsphere-network /NUCDC/network/DPortGroup 1 --vmwarevsphere-datacenter /NUCDC --vmwarevsphere-disk-size 20000 --vmwarevsphere-ssh-password tcuser --vmwarevsphere-folder /NUCDC/vm/test folder/k8s vms --vmwarevsphere-memory-size 2048 --vmwarevsphere-pool /NUCDC/host/esxi01.ansil.io/Resources --vmwarevsphere-creation-type library --vmwarevsphere-password Vmware@123 --vmwarevsphere-ssh-user-group staff --vmwarevsphere-vcenter-port 443 --vmwarevsphere-content-library test content library --vmwarevsphere-ssh-port 22 --vmwarevsphere-ssh-user docker --vmwarevsphere-username administrator@ansil.io --vmwarevsphere-vcenter 192.168.110.40 --vmwarevsphere-clone-from ubuntu-18-cloud-template --vmwarevsphere-cpu-count 2 --vmwarevsphere-cloud-config /RDEVSVNQER/cloud-config all-in-one-node1]

• Rancher trace log rancher_node_driver_debug.log

• If there is a network adapter present in the VM template and that is mapped to an existing network, then VM comes up with that network instead of the one passed via node template.

Environment information

• Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.11
• Installation option (single install/HA): HA

gz#15111