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
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.
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