Monitoring operator degraded, Error: running task Updating Prometheus-k8s failed
Issue
- The monitoring operators are stuck in the degraded state.
- Reason: UpdatingPrometheusK8SFailed
- Rollout of the monitoring stack failed and is degraded
- Failed to rollout the stack. Error: running task Updating Prometheus-k8s failed:
- waiting for Prometheus object changes failed: waiting for Prometheus openshift-monitoring/k8s: expected 2 replicas, got 1 updated replicas
- err="open /etc/prometheus/config_out/prometheus.env.yaml: no such file or directory"
Logs
Operator: 'monitoring'
Issue : Not available
Reason : UpdatingPrometheusK8SFailed
Message : Rollout of the monitoring stack failed and is degraded. Please investigate the degraded status error.
LastTransition : 2022-03-05T00:19:33Z
Issue : Degraded
Reason : UpdatingPrometheusK8SFailed
Message : Failed to rollout the stack. Error: running task Updating Prometheus-k8s failed: waiting for Prometheus object changes failed: waiting for Prometheus openshift-monitoring/k8s: expected 2 replicas, got 1 updated replicas
LastTransition : 2022-03-05T00:19:33Z
Issue : Progressing
Reason : RollOutInProgress
Message : Rolling out the stack.
LastTransition : 2022-03-08T14:20:03Z
Lack of space in the node, see no space left on device
$ oc get events -n openshift-monitoring
LAST SEEN TYPE REASON OBJECT MESSAGE
2m1s Warning Unhealthy pod/prometheus-k8s-0 (combined from similar events): Readiness probe failed: time="2022-03-08T14:27:14Z" level=error msg="exec failed: open /var/run/crio/exec-pid-dir/.06f0c7d1cdfdbcce6d924e027319bf7267ee333d4ce26e70d9d650c1a89f66354cd9721e-c273-4da2-8b9e-9ea69319707e: no space left on device"
Environment
- Red Hat OpenShift Container Platform 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.