Description of problem: CVO fires and alert `ClusterOperatorDown` due to authentication operator being down. More in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24602/pull-ci-openshift-origin-master-e2e-gcp/6053 Version-Release number of selected component (if applicable): 4.4 How reproducible: Often Steps to Reproduce: 1. Start a cluster 2. Run e2e test suite Actual results: Test suite fails due to alert being fired Expected results: Test suite passes and no `ClusterOperatorDown` alerts are being fired. Additional info: This is often preventing merges in openshift/origin repository.
What does `ClusterOperatorDown` mean? What are the conditions that need to apply for a component to report that?
From alert I can only see one condition: `cluster_operator_up{job="cluster-version-operator"} == 0`, but I don't know how this metric work. Possibly team responsible for cluster-version-operator has more information as this is coming directly from CVO.
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-2020:0581