-
Bug
-
Resolution: Done
-
Undefined
-
4.9.0
-
None
-
None
-
False
-
Description of problem:
node_exporter that can't be running on nodes that are offline/unavailable is one of the top reasons why CMO goes degraded. It would make sense to have CMO correlate the number of running node_exporter pods with the status of the nodes and not go degraded if the node_exporter pods are running on all nodes which are ready. As an example, if the cluster has N nodes with one node being not ready and (N-1) node_exporter pods are running then CMO should report Available rather than Degraded.
Version-Release number of selected component (if applicable):
How reproducible:
Always when nodes are offline.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Backport clone of https://issues.redhat.com/browse/OCPBUGSM-32497
- blocks
-
OCPBUGS-3665 [Backport for 1986375] Avoid CMO being degraded when some nodes aren't available
- Closed