With the same symptoms of OCPBUGS-18641, but this time creating new nodes with the usage of machineset which have more than one NIC it ends up leaving the taint "node.cloudprovider.kubernetes.io/uninitialized" and misses the ProviderID value.

As been noticed that in 4.13 in addition to the already explained symptoms, the vmware-vsphere-csi-driver-node goes in "CrashLoopBackOf" due to [Error: virtual machine wasn't found] while in 4.14 this does not happen.

Very often

    1. Install an IPI cluster on VMware
    2. Create/Modify machineset with two network interfaces
    3. Scale out the machineset

- Nodes get created with taint "node.cloudprovider.kubernetes.io/uninitialized"
- ProviderID is missing in the node definition
- vmware-vsphere-csi-driver-node goes in CrashLoopBackOf" due to [Error: virtual machine wasn't found]

The nodes should get created without the taint, with the ProviderID and without pods failing