Bug 1717619 - Telemetry should include the condition reason on degraded operators
Summary: Telemetry should include the condition reason on degraded operators
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.z
Assignee: Clayton Coleman
QA Contact: liujia
Depends On:
TreeView+ depends on / blocked
Reported: 2019-06-05 19:56 UTC by Clayton Coleman
Modified: 2019-07-04 09:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-07-04 09:01:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1635 None None None 2019-07-04 09:01:33 UTC

Description Clayton Coleman 2019-06-05 19:56:08 UTC
This bug was initially created as a copy of Bug #1717617

I am copying this bug because: it should be part of 4.1.z so that we can triage failures.

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 liujia 2019-06-20 08:43:53 UTC
Version: 4.1.0-0.nightly-2019-06-19-220253

According to pr197, Checked from prometheus console that "reason" section was added into cluster_operator_conditions metric now.


Verify the bug according to my understanding, please feel free to re-open it if it's not expected.

Comment 4 errata-xmlrpc 2019-07-04 09:01:24 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.


Note You need to log in before you can comment on or make changes to this bug.