Bug 1741821

Summary: Usage Report table values are not shown correctly
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: David Taylor <dtaylor>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, pruan, yapei
Target Milestone: ---Keywords: Regression
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:36:19 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:
Attachments:
Description Flags
UsageReportTable none

Description Yadan Pei 2019-08-16 07:45:12 UTC 
Description of problem:
Usage Report table show data in wrong column

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

How reproducible:
Always

Steps to Reproduce:
1. cluster admin enable Metering, then goes to Administration -> Chargeback -> Create report using example report YAML
2. After report is successfully generated, view report details


Actual results:
2. in Usage Report table, some namespace link data are shown in peirod start column, some in data start column etc

Expected results:
2. data should be shown in corresponding column

Additional info:
Comment 1 Yadan Pei 2019-08-16 07:45:40 UTC 
Created attachment 1604305 [details]
UsageReportTable
Comment 2 Samuel Padgett 2019-08-16 12:22:43 UTC 
This looks like Bug 1736501. Are you running with the fix https://github.com/operator-framework/operator-metering/pull/895 for metering?
Comment 3 David Taylor 2019-08-19 15:11:39 UTC 
Hi, you need to do a manual install of the latest operator-metering code to enable Metering and to get Chance's #895 fix. 
You cannot install Metering via OLM which is still at v4.1, you must do a manual install: https://github.com/operator-framework/operator-metering/blob/master/Documentation/manual-install.md
Comment 4 Peter Ruan 2019-08-19 19:03:06 UTC 
this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1736501 which I have verified the fix already.  Test case (https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-24821) has been added and automation (https://github.com/openshift/cucushift/pull/7079) added to address the issue
Comment 5 Yadan Pei 2019-08-20 01:07:08 UTC 
Thank you all!
Comment 6 errata-xmlrpc 2019-10-16 06:36:19 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