Bug 1809699

Summary: No controller metrics reported from 4.3 openshift-controller-manager
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: openshift-controller-managerAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED ERRATA QA Contact: wewang <wewang>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.3.zCC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: openshift-controller-manager metrics were not properly registered with the 1.16 kubernetes Prometheus registry Consequence: metrics for openshift control plane controllers were missing Fix: properly registered openshift-controller-manager metrics with Prometheus Result: restored openshift control plane metrics
Story Points: ---
Clone Of:
: 1810304 (view as bug list) Environment:
Last Closed: 2020-07-13 17:17:45 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: 1810304    
Attachments:
Description Flags
Metrics from 4.3 cluster OCM leader none

Description Clayton Coleman 2020-03-03 17:23:49 UTC
Created attachment 1667268 [details]
Metrics from 4.3 cluster OCM leader

On a 4.3 cluster experiencing issues we tried to pull metrics from the openshift controllers and realized none of them were being reported.  The pods are being scraped, but the metrics endpoint is only returning a very small set of metrics.  It looks like we are failing to correctly register our metrics.

The linked attachment contains all the metrics reported from this 4.3 cluster, but metrics that should be there are missing (like image import controller metrics).

Urgent because we can't alert or debug if these are missing.

Comment 6 errata-xmlrpc 2020-07-13 17:17:45 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-2020:2409