olm-operator is in CrashLoopBackOff state

Solution Verified - Updated -

Issue

  • The container olm-operator is in CrashLoopBackOff state after updating to 4.15
  • Restarting the olm-operator-<replicasetid>-<id> POD does not solve the issue.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • >= 4.15

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