Bug 1601590

Summary: Incorrect chargeback metric values displayed for recently created vsphere vm
Product: Red Hat CloudForms Management Engine Reporter: Tasos Papaioannou <tpapaioa>
Component: ReportingAssignee: Libor Pichler <lpichler>
Status: CLOSED ERRATA QA Contact: Tasos Papaioannou <tpapaioa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, dmetzger, gtanzill, obarenbo, simaishi
Target Milestone: GAKeywords: Regression
Target Release: 5.10.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.10.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:03:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Tasos Papaioannou 2018-07-16 19:20:51 UTC 
Description of problem:

A recently-created VM with imported historical capture data will show incorrect values for, e.g., CPU Used and Memory Used values in chargeback reports. The columns for the actual costs are correct, however. This is fixed by the following commit, which is in 5.10.0 but not 5.9.3 or 5.9.4:

https://github.com/ManageIQ/manageiq/pull/17620
https://github.com/ManageIQ/manageiq/commit/d35b0519071607d1d4258c4428fae766c40c31e1

Version-Release number of selected component (if applicable):

5.9.3.4 and 5.9.4.0

How reproducible:

100%

Steps to Reproduce:
1.) With initial_capture_days set to 30, add a vsphere provider that has historical vm metric data.
2.) Assign default chargeback rates to the enterprise, and create a chargeback report that displays cpu and memory usage and costs.
3.) Run chargeback report and view results.

Actual results:

Values for cpu used and memory used are much higher than expected, and don't match the displayed costs.

Expected results:

Correct usage displays in chargeback report.

Additional info:
Comment 5 Tasos Papaioannou 2018-09-07 15:56:50 UTC 
Verified on 5.10.0.14.
Comment 6 errata-xmlrpc 2019-02-07 23:03:30 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/RHSA-2019:0212