Bug 1740357

Summary: Auth operator reporting unavailable and reason "available"
Product: OpenShift Container Platform Reporter: Ben Parees <bparees>
Component: apiserver-authAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: scheng
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, mfojtik, scheng
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: auth-operator reported a static "available" string as a reason for the unavailability condition. Consequence: the reason of unavailability of the operator was unclear. Fix: more precise reasons are implemented. Result: the reason describes why the operator reported unavailability.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:05:05 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:

Description Ben Parees 2019-08-12 18:13:29 UTC 
Description of problem:
16 clusters in telemeter are reporting the auth operator as unavailable and with a reason of "available"

Version-Release number of selected component (if applicable):
Doesn't seem to be a way to drill into the specific clusters in telemter

How reproducible:
Always?

Actual results:
operator is unavailable and reason is not useful


Expected results:
operator should be available, and if it's not, the reason should indicate why


Additional info:
There are two asks here:

1) determine why the operator is unavailable in those 16 clusters
2) fix the reason reporting
Comment 2 Michal Fojtik 2019-08-21 14:07:39 UTC 
I was not able to find the code that does this in the current version of auth operator, so I assume this is fixed in the latest version.
This is part of the technical debt we are going to tackle in 4.3.
Comment 8 errata-xmlrpc 2020-01-23 11:05:05 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:0062