Prometheus pods remain in CrashLoopBackOff

Solution Verified - Updated -

Issue

  • Prometheus pods cannot start and remains in CrashLoopBackOff.
  • Pod logs show the error "Opening storage failed open /prometheus/01HGTDKP8IYT1ELLOA8BYUYKAQ/meta.json: no such file or directory".
  • Prometheus pods are running out of memory.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 3.11
    • 4
  • Prometheus

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