Bug 1741645 - Telemetry should include the ClusterVersion conditions with reasons
Summary: Telemetry should include the ClusterVersion conditions with reasons
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.2.0
Assignee: Abhinav Dahiya
QA Contact: liujia
Depends On:
Blocks: 1741661
TreeView+ depends on / blocked
Reported: 2019-08-15 17:25 UTC by W. Trevor King
Modified: 2019-10-16 06:36 UTC (History)
2 users (show)

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

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-version-operator pull 236 0 None closed Bug 1741645: pkg/cvo/metrics: Report cluster-version conditions with reasons 2020-03-18 04:59:43 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:36:26 UTC

Description W. Trevor King 2019-08-15 17:25:43 UTC
Bug 1717617 (4.2) and bug 1717619 (4.1.z) added Telemetry for ClusterOperator conditions.  We should add it for ClusterVersion conditions as well, so we can get things like UpdatePayloadClusterError reasons [1] out of Telemetry without requiring cluster access for 'oc get' or must-gather commands.

I expect we'll want to backport this to 4.1.z via a cloned bug, and the implementation should apply cleanly there, but this bug is just about 4.2.

[1]:  https://bugzilla.redhat.com/show_bug.cgi?id=1740838#c20

Comment 2 liujia 2019-08-19 07:29:45 UTC
Version: 4.2.0-0.nightly-2019-08-18-222019

According to pr236, checked "version" operator was added into cluster_operator_conditions metric too.
Element                                   Value
cluster_operator_conditions{condition="Available",endpoint="metrics",instance="",job="cluster-version-operator",name="version",namespace="openshift-cluster-version",pod="cluster-version-operator-956b48c68-xjf74",service="cluster-version-operator"} 1
cluster_operator_conditions{condition="Failing",endpoint="metrics",instance="",job="cluster-version-operator",name="version",namespace="openshift-cluster-version",pod="cluster-version-operator-956b48c68-xjf74",service="cluster-version-operator"}  0
cluster_operator_conditions{condition="Progressing",endpoint="metrics",instance="",job="cluster-version-operator",name="version",namespace="openshift-cluster-version",pod="cluster-version-operator-956b48c68-xjf74",service="cluster-version-operator"}  0
cluster_operator_conditions{condition="RetrievedUpdates",endpoint="metrics",instance="",job="cluster-version-operator",name="version",namespace="openshift-cluster-version",pod="cluster-version-operator-956b48c68-xjf74",reason="RemoteFailed",service="cluster-version-operator"}  0

All conditions of "version" comply with the clusterversion object.
# ./oc get clusterversion -o json|jq ".items[0].status.conditions"
    "lastTransitionTime": "2019-08-19T05:48:38Z",
    "message": "Done applying 4.2.0-0.nightly-2019-08-18-222019",
    "status": "True",
    "type": "Available"
    "lastTransitionTime": "2019-08-19T05:44:02Z",
    "status": "False",
    "type": "Failing"
    "lastTransitionTime": "2019-08-19T05:48:38Z",
    "message": "Cluster version is 4.2.0-0.nightly-2019-08-18-222019",
    "status": "False",
    "type": "Progressing"
    "lastTransitionTime": "2019-08-19T05:35:26Z",
    "message": "Unable to retrieve available updates: currently installed version 4.2.0-0.nightly-2019-08-18-222019 not found in the \"stable-4.2\" channel",
    "reason": "RemoteFailed",
    "status": "False",
    "type": "RetrievedUpdates"

Comment 3 errata-xmlrpc 2019-10-16 06:36:15 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.