ClusterObservability and perses operator pod in CrashLoopBackOff due to OOMKilled in RHOCP4

Solution Verified - Updated -

Issue

  • After upgrade of COO to version 1.1.0, observability-operator & perses-operator pods are in CrashLoopBackOff due to OutOfMemory Error.

    oc get pods -n openshift-cluster-observability-operator | grep -v Running

NAME                                                         READY   STATUS             RESTARTS   AGE
observability-operator-757b8565d4-g5mzx                      0/1     CrashLoopBackOff   5          18m
perses-operator-666859f6-248bj                               0/1     CrashLoopBackOff   17         1h

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Cluster Observability Operator (COO)
    • 1.1
    • 1.2

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