[RHOCP 4] "istio-cni-node-xxxx" pod shows "CNI installer fails if /etc/cni/multus/net.d/ doesn't exist" error in OpenShift Service Mesh

Solution Verified - Updated -

Issue

  • After updating the OpenShift cluster from v4.11 to v4.12 issue is observed with istio-cni-node-xxx pods on newly created workers, pods are stuck in CrashLoopBackOff
  • New installation of SMCP v2.2 using the OSSM v2.4 operator version has Istio-CNI pods in openshift-operators projects in CrashLoopBackOff state.
  • Adding a New Node to an existing cluster running SMCP v2.2 with OSSM v2.4 leaves istio-cni pods in CrashLoopBackOff state

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Service Mesh (OSSM)
    • 2.4

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