Bug 1745865

Summary: Pods by Storage gives No datapoints found
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Rastislav Wagner <rawagner>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:37:54 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:

Description Yadan Pei 2019-08-27 06:12:23 UTC
Description of problem:
When show Top Consumer Pods by Storage, it returns No datapoints found

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-25-233755

How reproducible:
Always

Steps to Reproduce:
1. Cluster admin visit Home -> Dashboards, check Top Consumers table
2. Show Top Consumers Pods -> By Storage


Actual results:
2. It returns "No datapoints found", currently the query expression is:
sort_desc(avg by (pod_name)(irate(container_fs_io_time_seconds_total{container_name="POD", pod_name!=""}[1m])))

Expected results:
2. query expression should return correct data

Additional info:

Comment 2 Yadan Pei 2019-09-02 01:58:33 UTC
$ oc adm release info registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-09-01-224700 --commits | grep console
  console                                       https://github.com/openshift/console                                       821d11c1a1cef7ea0e568ed8f2301c546a47d90a
  console-operator                              https://github.com/openshift/console-operator                              320d99ef571b200ac8528206086572bbf9e094fa

$ cd /path/to/console/repo; git pull
$ git log 821d11c1a1cef7ea0e568ed8f2301c546a47d90a | grep '#2483'    // PR is not found

Comment 3 Yadan Pei 2019-09-03 09:07:51 UTC
Changes is picked up in 4.2.0-0.nightly-2019-09-02-172410, now it doesn't show 'No datapoints found'

But all data are in 0ns, this is tracked in another bug 1748260


The original reported issue has been fixed

Comment 4 errata-xmlrpc 2019-10-16 06:37:54 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-2019:2922