Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1717617

Summary: Telemetry should include the condition reason on degraded operators
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: Cluster Version OperatorAssignee: Abhinav Dahiya <adahiya>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, bleanhar, jokerman, juzhao, mmccomas, wking
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:31:27 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:    
Bug Blocks: 1741062    
Attachments:
Description Flags
all 4.1 ClusterOperator info none

Description Clayton Coleman 2019-06-05 19:54:55 UTC 
While assessing 4.1.0 GA degraded operators Adam suggested capturing the reason (which has bounded cardinality) on the telemetry metric for cluster_operator_conditions, which would

1. incentivize teams to add good reasons
2. allow a quick summarization of why the operator is degraded

Added in https://github.com/openshift/cluster-version-operator/pull/197, should be back ported to 4.1.1
Comment 2 Junqi Zhao 2019-07-03 05:34:40 UTC 
Created attachment 1586914 [details]
all 4.1 ClusterOperator info
Comment 6 W. Trevor King 2019-08-15 18:38:50 UTC 
Bug 1717619 is about 4.1.z.  This bug and https://github.com/openshift/cluster-version-operator/pull/197 is about 4.2.0.  I'm fixing the target release and pushing back to ON_QA to get double-checking on a 4.2 nightly.
Comment 10 errata-xmlrpc 2019-10-16 06:31:27 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