After Upgrading RHOCP Cluster to 4.14.25, metal3 Pod is in CrashLoopBackOff State

Solution Verified - Updated -

Issue

Following the cluster upgrade, the metal3 pod within the openshift-machine-api namespace becomes stuck in the CrashLoopBackOff state.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.14.25
  • BareMetal with FIPS enabled.

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