Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1618634 - [admin] Some metrics data are empty
[admin] Some metrics data are empty
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring (Show other bugs)
3.11.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Frederic Branczyk
Junqi Zhao
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-17 03:41 EDT by Yadan Pei
Modified: 2018-10-11 03:25 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:25:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
EmptyData1 (203.61 KB, image/png)
2018-08-17 03:44 EDT, Yadan Pei
no flags Details
EmptyData2 (157.26 KB, image/png)
2018-08-17 03:45 EDT, Yadan Pei
no flags Details
nodes metrics (148.70 KB, image/png)
2018-08-26 22:27 EDT, Junqi Zhao
no flags Details
pod metrics (126.47 KB, image/png)
2018-08-26 22:28 EDT, Junqi Zhao
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:25 EDT

  None (edit)
Description Yadan Pei 2018-08-17 03:41:08 EDT
Description of problem:
Empty data shown for CPU,Memory and Disk Usage on Home, Node CPU, Network, RAM data are also empty

Version-Release number of selected component (if applicable):
registry.reg-aws.openshift.com:443/openshift3/ose-console                   v3.11               e5f3dbab56b30       288MB
openshift v3.11.0-0.16.0

How reproducible:
Always

Steps to Reproduce:
1.Enable Cluster Monitoring
# oc get pods -n openshift-monitoring
NAME                                           READY     STATUS    RESTARTS   AGE
alertmanager-main-0                            3/3       Running   0          52m
alertmanager-main-1                            3/3       Running   0          51m
alertmanager-main-2                            3/3       Running   0          51m
cluster-monitoring-operator-7f956789fc-xk6hf   1/1       Running   0          1h
grafana-6bd78bcd6d-x2lr2                       2/2       Running   0          1h
kube-state-metrics-58d4dd6b44-gt288            3/3       Running   0          51m
node-exporter-2rsml                            2/2       Running   0          51m
node-exporter-hwnpq                            2/2       Running   0          51m
node-exporter-zwk4h                            2/2       Running   0          51m
prometheus-k8s-0                               4/4       Running   1          1h
prometheus-k8s-1                               4/4       Running   1          52m
prometheus-operator-7fff695789-zv7bb           1/1       Running   0          1h
2.Login to admin console with cluster-admin
3.Browse to Home -> Status
4.Browse to Nodes Overview page

Actual results:
3. Some metrics charts such as API Servers Up, Alerts Firing, API Request Success Rate are shown with correct data, but CPU Usage, Memory Usage and Disk Usage are with empty value. It looks like the query expression used wrong variables which leads to "No datapoints found" thus empty value

Several Graph errors eg:
Graph error: No data from query (sum(node_filesystem_size{device!="rootfs"}) - sum(node_filesystem_free{device!="rootfs"})) / sum(node_filesystem_size{device!="rootfs"}) * 100

4.CPU, RAM, Network In, Network Out, FileSystem data are empty
base.jsx:12 Graph error: No data from query for RAM.
base.jsx:12 Graph error: No data from query for CPU.
base.jsx:12 Graph error: No data from query for Network In.
base.jsx:12 Graph error: No data from query for Network Out.
base.jsx:12 Graph error: No data from query for Filesystem.


Expected results:
3-4. Correct query expression should be used and data should be shown correctly

Additional info:
Comment 1 Yadan Pei 2018-08-17 03:44 EDT
Created attachment 1476569 [details]
EmptyData1
Comment 2 Yadan Pei 2018-08-17 03:45 EDT
Created attachment 1476570 [details]
EmptyData2
Comment 3 Samuel Padgett 2018-08-17 09:38:06 EDT
Transitioning to Monitoring because it looks like the console requests are correct, just that Prometheus isn't returning any data.
Comment 4 Frederic Branczyk 2018-08-17 09:42:25 EDT
Are you getting an actual error or just an empty result? A user needs appropriate RBAC permissions (view ClusterRole should be sufficient).
Comment 5 Junqi Zhao 2018-08-20 04:46:32 EDT
maybe related to Bug 1619132
Comment 6 Frederic Branczyk 2018-08-20 06:33:20 EDT
Yes I believe Junqi is correct, I believe this is the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1619132
Comment 7 Yadan Pei 2018-08-23 01:55:09 EDT
> Are you getting an actual error or just an empty result? A user needs appropriate RBAC permissions (view ClusterRole should be sufficient).

I'm getting empty data on console and error info base.jsx:12 Graph error: No data from query for RAM/CPU.... in browser dev console, I use cluster-admin to view metric

>Yes I believe Junqi is correct, I believe this is the same problem as

Thanks, I will wait for bug 1619132 to be resolved
Comment 8 Frederic Branczyk 2018-08-23 05:52:54 EDT
We just merged a number of pull requests that should fix most of these problems. We also noticed some incorrect behavior for filesystem graphs that is already in the works, I would suggest to create a new issue for that though.
Comment 9 Frederic Branczyk 2018-08-23 15:34:51 EDT
All relevant pull requests for this have now been merged. Please go ahead and test this.
Comment 10 Junqi Zhao 2018-08-26 22:26:17 EDT
Please change to ON_QA, issue is fixed,see the attached picture

cluster monitoring version: v3.11.0-0.22.0.0
# openshift version
openshift v3.11.0-0.22.0
Comment 11 Junqi Zhao 2018-08-26 22:27 EDT
Created attachment 1478846 [details]
nodes metrics
Comment 12 Junqi Zhao 2018-08-26 22:28 EDT
Created attachment 1478847 [details]
pod metrics
Comment 13 Junqi Zhao 2018-08-27 20:18:12 EDT
Per Comment 10 - Comment 12, set to VERIFIED
Comment 15 errata-xmlrpc 2018-10-11 03:25:20 EDT
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-2018:2652

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