OLM pod is stuck in CrashLoopBackOff state on OpenShift Container Platform 4
Issue
-
Updating OpenShift - Logging is failing because the OLM Operator pod is in
CrashLoopBackOff
state, reporting the below error.time="2021-06-04T16:26:12Z" level=fatal msg="couldn't cleanup cross-namespace ownerreferences" error="stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 263; INTERNAL_ERROR"
Environment
- Red Hat OpenShift Container Platform 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.