Description of problem: Rule : kubelet_volume_stats_available_bytes{job="kubelet",namespace=~"(openshift.*|kube.*|default|logging)"} and predict_linear(kubelet_volume_stats_available_bytes{job="kubelet",namespace=~"(openshift.*|kube.*|default|logging)"}[6h], 4 * 24 * 3600) < 0 Alert : alertname="KubePersistentVolumeFullInFourDays" 15:46:20, 2018-11-09 Labels : severity="critical" service="kubelet" prometheus="openshift-monitoring/k8s" persistentvolumeclaim="datadir-mysql-0" namespace="kube-system" job="kubelet" instance="194.13.15.207:10250" exported_namespace="gams-sanofi" endpoint="https-metrics" cluster="scale-ocp-prod" message: Based on recent sampling, the persistent volume claimed by datadir-mysql-0 in namespace kube-system is expected to fill up within four days. Currently 1.3514752e+08 bytes are available. Also note that disk space may be better no be exprimed in Mo or Go that bytes. Version-Release number of selected component (if applicable): Openshift 3.11 Steps to Reproduce: - create a new projet - create a small PV - Put a/some big files on it - Wait for the alert to be triggered Actual results: Expected results: To be triggered only at the described namespaces. Additional info:
Sorry for the inconvenience, this has already been merged to be fixed in a 3.11.z release: https://github.com/openshift/cluster-monitoring-operator/pull/127
Hi Frederic, Thank you for letting me know. Do we have an ETA for the next ERRATA where the fix is implemented?
I'm not aware of the schedule for z-stream releases, that question would need to go to the respective team taking care of that.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3139