+++ This bug was initially created as a clone of Bug #2052270 +++ The new condition landed in the dev branch [1] after 4.9 forked off and before 4.10 forked off, so 4.10 and later are impacted. There are a few issues with the current implementation: * Some "treshold" -> "threshold" typos. * The "etcd disk metrics exceeded..." reasons [1] aren't the CamelCase slugs reason expects [2]. * It seems that the condition may not get cleared once latency returns to reasonable levels, although no exact code links to back this one up. ... [1]: https://github.com/openshift/cluster-etcd-operator/pull/687/files#diff-1ffe8d5a41289fd1acde2f0fcd5d53c842caffe41d70a478e82b018977b6ac14R127 [2]: https://github.com/openshift/api/blob/7e3ffb09accd36fb0536fa0e69bed5d70cccd6e5/config/v1/types_cluster_operator.go#L131 --- Bug 2052270 is covering the first point. This bug series picks up the second point. A later bug cloned from 2052270 will pick up the third point. All of these series should probably be backported to 4.10.z.
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069