-
Bug
-
Resolution: Done
-
Undefined
-
4.10, 4.9
-
None
-
-
-
None
-
False
-
Description of problem:
kube_daemonset_updated_number_scheduled got renamed to kube_daemonset_status_updated_number_scheduled in 4.9, but the definition of KubeDaemonSetRolloutStuck didn't get updated up until 4.11 https://github.com/openshift/cluster-monitoring-operator/commit/35ffa690cec23d6a708aafea36a2d8b77f8a8556 .
Version-Release number of selected component (if applicable):
How reproducible:
Always
We suggest backporting the fix at least to 4.10, as it can affect both customers and ours ability to detect and troubleshoot certain issues, both from single-cluster as well as from the fleet-wide longer-term trends perspective point of view.
- clones
-
OCPBUGS-344 KubeDaemonSetRolloutStuck alert using incorrect metric in 4.9 and 4.10
- Closed
- is cloned by
-
OCPBUGS-450 KubeDaemonSetRolloutStuck alert using incorrect metric in 4.9 and 4.10
- Closed
- is depended on by
-
OCPBUGS-450 KubeDaemonSetRolloutStuck alert using incorrect metric in 4.9 and 4.10
- Closed