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:
Verified on 5.10.0.14.
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