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:
Version-Release number of selected component (if applicable):
188.8.131.52 and 184.108.40.206
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.
Values for cpu used and memory used are much higher than expected, and don't match the displayed costs.
Correct usage displays in chargeback report.
Verified on 220.127.116.11.
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.