Bug 1646562 - Bad field name format for chargeback rates
Summary: Bad field name format for chargeback rates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.10.0
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: Libor Pichler
QA Contact: juwatts
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 16:33 UTC by Tasos Papaioannou
Modified: 2019-12-12 13:34 UTC (History)
6 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:34:23 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:34:40 UTC

Description Tasos Papaioannou 2018-11-05 16:33:13 UTC
Description of problem:

In 5.10.0, new chargeback report fields were added:

Cpu Allocated Rate
Cpu Used Rate
Disk Io Used Rate
Net Io Used Rate

The formats of these names are inconsistent with the existing fields, and should be:

CPU Allocated Rate
CPU Used Rate
Disk I/O Used Rate
Network I/O Used Rate


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

5.10.0.22

How reproducible:

100%

Steps to Reproduce:
1.) Create or edit a report based on 'Chargeback for Vms' and view the Available Fields dropdown.

Actual results:

See above.

Expected results:

See above.

Additional info:

Comment 3 juwatts 2019-07-02 15:58:41 UTC
Verified in  5.11.0.11.20190625161125_392c61e

The following are now available fields:
vCPUs Allocated Rate
CPU Used Rate
Disk I/O Used
Network I/O Used Rate

Comment 5 errata-xmlrpc 2019-12-12 13:34:23 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:4199


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