Bug 1740363 - 59 degraded auth operators in telemeter
Summary: 59 degraded auth operators in telemeter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Stefan Schimanski
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks: 1743418
TreeView+ depends on / blocked
 
Reported: 2019-08-12 18:19 UTC by Ben Parees
Modified: 2019-10-16 06:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1743418 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:35:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 179 0 'None' closed Bug 1740363: Use specific reasons for all route degraded errors 2020-02-05 04:43:39 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:35:53 UTC

Comment 2 Michal Fojtik 2019-08-19 08:53:36 UTC 
I've created https://github.com/openshift/cluster-authentication-operator/pull/177 to expand the list of possible reasons we see these degraded clusters.
Comment 4 Chuan Yu 2019-08-27 05:53:27 UTC 
The degraded reason print not very nice, such as:
Status:
  Conditions:
    Last Transition Time:  2019-08-27T03:31:42Z
    Message:               RouteHealthDegraded: failed to GET route: EOF
    Reason:                RouteHealthDegradedFailedGet
    Status:                True
    Type:                  Degraded

Do we need colon seperate the reason, like this:

    Reason:                RouteHealthDegraded: FailedGet

build version, 4.2.0-0.nightly-2019-08-26-202352
Comment 7 Chuan Yu 2019-08-27 09:07:01 UTC 
Verified on 4.2.0-0.nightly-2019-08-26-202352
Comment 8 Chuan Yu 2019-08-27 09:07:02 UTC 
Verified on 4.2.0-0.nightly-2019-08-26-202352
Comment 10 errata-xmlrpc 2019-10-16 06:35:39 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.