Bug 1843284 - Prometheus is not reporting router metrics
Summary: Prometheus is not reporting router metrics
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ibm-roks-toolkit
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.z
Assignee: Cesar Wong
QA Contact: Cesar Wong
URL:
Whiteboard:
Depends On: 1825029
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-03 00:54 UTC by OpenShift BugZilla Robot
Modified: 2020-06-23 00:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-23 00:57:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ibm-roks-toolkit pull 26 0 None closed [release-4.4] Add monitoring label to ingress namespace 2020-10-27 16:23:17 UTC
Red Hat Product Errata RHBA-2020:2580 0 None None None 2020-06-23 00:58:09 UTC

Description OpenShift BugZilla Robot 2020-06-03 00:54:14 UTC
+++ This bug was initially created as a clone of Bug #1825029 +++

Description of problem:
Router metrics are not getting scraped by Prometheus

How reproducible:
Always

Steps to Reproduce:
1. Run openshift e2e conformance against an IBM ROKS cluster

Actual results:
The following tests fail:
[Feature:Prometheus][Conformance] Prometheus when installed on the cluster should provide ingress metrics`,
[Conformance][Area:Networking][Feature:Router] The HAProxy router should enable openshift-monitoring to pull metrics`,


Expected results:
No tests fail

Additional info:

--- Additional comment from cewong on 2020-06-02 21:58:15 UTC ---

This is happening because the openshift-ingress namespace is missing the "openshift.io/cluster-monitoring: true" label.
We should be able to add this in the ibm-roks-toolkit code.

Comment 3 XiuJuan Wang 2020-06-16 10:32:50 UTC
Anyone could help check this bug? This bug is in 4.4.9 errata list, it need release out at Jun 22th.
Thank you!

Comment 4 Cesar Wong 2020-06-16 13:25:41 UTC
Verified this in 4.4

Comment 6 errata-xmlrpc 2020-06-23 00:57:50 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:2580


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