"prometheus-user-workload" Pod "crashloopbackoff" Due to Volume Exhaustion

Solution Verified - Updated -

Issue

One of the prometheus-user-workload pods was in crashloopbackoff state due to insufficient storage in its PVC with the below error:

2024-07-19T03:07:03.322605873Z unexpected fault address 0x7fd79df3d000
2024-07-19T03:07:03.322605873Z fatal error: fault
2024-07-19T03:07:03.322947770Z [signal SIGBUS: bus error code=0x2 addr=0x7fd79df3d000 pc=0x476862]

The pod logs indicate a SIGBUS error, suggesting memory access violations related to storage exhaustion.

Environment

  • Red Hat OpenShift Container Platform 4
  • prometheus-user-workload Pods

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