Nodes with multiple network interfaces on vSphere show taint "node.cloudprovider.kubernetes.io/uninitialized" in RHOCP4.

Solution Verified - Updated -

Issue

  • Scaling up RHOCP nodes with multiple network interfaces results not linked to the machine object.

  • Scaling nodes with multiple NICs can create vmware-vsphere-csi-driver-node-XXXX PODs in a CrashLoopBackOff state.

  • After upgrading to RHOCP 4.14 on the vSphere environment the scaling of nodes with multiple interfaces stopped to fully work.

  • Newly provisioned Nodes after RHOCP upgrade to version 4.14, does not have the Provider ID

    $ oc get nodes -o json | jq '.items[]|[.metadata.name, .spec.providerID]'
    
    [
      "ocpnode-43210-master-0",
      "vsphere://4200xxxx-2xxx-xxxx-xxxx-xxxxxxxxxxxx"
    ]
    [
      "ocpnode-43210-worker-0",
      null
    ]
    [
      "ocpnode-43210-worker-1",
      null
    ]
    [
      "ocpnode-43210-master-3",
      "vsphere://4200xxxx-2xxx-xxxx-xxxx-xxxxxxxxxxxx"
    ]
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • VMware vSphere

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content