Bug 2074084

Summary: CMO metrics not visible in the OCP webconsole UI
Product: OpenShift Container Platform Reporter: Tomas Remes <tremes>
Component: MonitoringAssignee: Haoyu Sun <hasun>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11CC: amuller, anpicker, aos-bugs, hasun, hongyli, spasquie
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:05:57 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:

Description Tomas Remes 2022-04-11 13:46:52 UTC
Description of problem:

I guess that the metrics ("cluster_monitoring_operator_last_reconciliation_successful" and "cluster_monitoring_operator_reconcile_attempts_total") registered by the CMO should be visible in the cluster metrics in the OCP webconsole. This is not true at the moment. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 hongyan li 2022-04-14 07:32:40 UTC
Tested with PR

Comment 8 Junqi Zhao 2022-04-18 08:05:09 UTC
fix is in 4.11.0-0.nightly-2022-04-16-163450,
# token=`oc sa get-token prometheus-k8s -n openshift-monitoring`
# oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://thanos-querier.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep cluster_monitoring_operator

# oc -n openshift-monitoring get service cluster-monitoring-operator -o jsonpath="{.spec.selector}"

# oc -n openshift-monitoring get servicemonitor cluster-monitoring-operator -o jsonpath="{.spec.selector.matchLabels}"

Comment 12 errata-xmlrpc 2022-08-10 11:05:57 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.