sriov-cni complains GLIBC_2.32 not found while upgrading to OCP 4.14

Solution Unverified - Updated -

Issue

  • SR-IOV workloads unable to start when upgrading from OCP 4.12 to OCP 4.14
  • sriov-cni complains 'GLIBC_2.32' not found, prevents the Pods from running
  • This problem happens if the SR-IOV Operator is upgraded before worker nodes upgrade

Environment

  • Red Hat OpenShift Container Platform 4.x
  • SR-IOV Operator

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