Custom prometheus pods stuck in `Init:0/1` with FailedMount due to `ReadWriteOnce` PVC conflict in RHOCP4

Solution Verified - Updated -

Issue

  • Prometheus pods fail to start after a rollout restart in a custom namespace.

  • New pods remain in Init:0/1 state with the following error.

    Warning   FailedMount   pod/prometheus-xxxxx   Unable to attach or mount volumes: unmounted volumes=[prometheus-db-volume], unattached volumes=[prometheus-db-volume], failed to process volumes=[]: timed out waiting for the condition

Environment

  • Red Hat OpenShift Container Platform 4 (RHOCP)

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