Bug 1601590 - Incorrect chargeback metric values displayed for recently created vsphere vm
Summary: Incorrect chargeback metric values displayed for recently created vsphere vm
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.9.0
Hardware: All
OS: All
Target Milestone: GA
: 5.10.0
Assignee: Libor Pichler
QA Contact: Tasos Papaioannou
Depends On:
TreeView+ depends on / blocked
Reported: 2018-07-16 19:20 UTC by Tasos Papaioannou
Modified: 2019-06-17 17:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-02-07 23:03:30 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 None None None 2019-02-07 23:03:37 UTC

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:


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

How reproducible:


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

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.


Note You need to log in before you can comment on or make changes to this bug.