Bug 1807467

Summary:	Authentication operator reported as down by CVO
Product:	OpenShift Container Platform	Reporter:	Pawel Krupa <pkrupa>
Component:	apiserver-auth	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED ERRATA	QA Contact:	scheng
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, mfojtik, slaznick
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1809193 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:42:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1809193
Bug Blocks:

Description Pawel Krupa 2020-02-26 12:37:09 UTC

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.

Comment 1 Standa Laznicka 2020-02-26 13:47:09 UTC

What does `ClusterOperatorDown` mean? What are the conditions that need to apply for a component to report that?

Comment 2 Pawel Krupa 2020-02-26 16:26:49 UTC

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.

Comment 11 errata-xmlrpc 2020-05-04 11:42:25 UTC

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