The monitoring CO degraded due to one of the prometheus-user-workload pods going in CrashLoopBackOff state in RHOCP 4

Solution Verified - Updated -

Issue

  • The monitoring CO degraded with the below error due to one of the prometheus-user-workload pods going into CrashLoopBackOff state:
$ oc get co monitoring
monitoring                                 4.14.22   False       True          True       3h20m    reconciling Prometheus Operator Admission Webhook Deployment failed: updating Deployment object failed: waiting for DeploymentRollout of openshift-monitoring/prometheus-operator-admission-webhook: context deadline exceeded

$ oc -n openshift-user-workload-monitoring get pods -l app.kubernetes.io/instance=user-workload -l  app.kubernetes.io/name=prometheus
NAME                         READY   STATUS             RESTARTS   AGE
prometheus-user-workload-0   6/6     Running            1          23m
prometheus-user-workload-1   5/6     CrashLoopBackOff   8          21m

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4

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