Bug 1388258 - VM GUID present multiple times in Chargeback reports
Summary: VM GUID present multiple times in Chargeback reports
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: Gregg Tanzillo
QA Contact: Nandini Chandra
URL:
Whiteboard: report:chargeback
Depends On:
Blocks: 1395851
TreeView+ depends on / blocked
 
Reported: 2016-10-24 21:38 UTC by Nandini Chandra
Modified: 2017-06-12 16:58 UTC (History)
5 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1395851 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:58:29 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
screen shot of chargeback report with VM GUID column (37.92 KB, image/png)
2016-10-24 21:38 UTC, Nandini Chandra
no flags Details

Description Nandini Chandra 2016-10-24 21:38:10 UTC
Created attachment 1213604 [details]
screen shot of chargeback report with VM GUID column

Description of problem:
----------------------
The 'VM GUID' column is present multiple times in Chargeback reports.I noticed that the column was present twice in one report and thrice in another.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Enable C&U collection for a provider.
2.Collect at least one hour's worth of C&U data in order to create a chargeback report.
3.Create a chargeback report for VMs.While creating the chargeback report, select 'VM GUID' as a field in the report.


Actual results:
--------------
'VM GUID' field is present multiple times in Chargeback reports.


Expected results:
----------------
'VM GUID' field should be present just once in Chargeback reports.


Additional info:
---------------

Comment 4 Nandini Chandra 2017-02-27 21:09:20 UTC
Verified in 5.8.0.2


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