OCP Virtualization VMs stuck in CrashLoopBackOff Status with Portworx storage

Solution In Progress - Updated -

Issue

  • Newly created VMs with Portworx storage stuck in CrashLoopBackOff
$ oc project

$ oc get vm
NAME        AGE     STATUS             READY
VM_1   6h23m   CrashLoopBackOff   False

  • This problem started after upgrading Portworx StorageCluster from 2.13 to 3.0.0.

  • virt-launcher pods failing to start with /lib64/libc.so.6: version 'GLIBC_2.34' not found (required by /etc/px_statfs.so)

Environment

  • OpenShift Virtualization 4.12
  • Portworx "Stork" StorageCluster 3.0.0.

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