Bug 1576101

Summary: total costs no longer showing in any chargeback report if they are the only columns in the report
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ReportingAssignee: Joe Rafaniello <jrafanie>
Status: CLOSED ERRATA QA Contact: Tasos Papaioannou <tpapaioa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: cpelland, fdewaley, gtanzill, jrafanie, mfeifer, obarenbo, tpapaioa, yrudman
Target Milestone: GAKeywords: ZStream
Target Release: 5.8.4   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1567254 Environment:
Last Closed: 2018-06-25 14:20:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 1567254    
Bug Blocks:    

Comment 3 CFME Bot 2018-05-14 13:30:55 UTC
New commit detected on ManageIQ/manageiq/fine:

commit 3c356a0336068b5a36a74ebfd65c62474214bf7a
Author:     Joe Rafaniello <jrafanie@redhat.com>
AuthorDate: Tue May  8 16:36:00 2018 -0400
Commit:     Joe Rafaniello <jrafanie@redhat.com>
CommitDate: Tue May  8 16:36:00 2018 -0400

    Check all costs fields for relevancy for the report

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1576101

    Manual backport of #17387

    If a user asks only for some of the fields (memory cost) in a chargeback report
    and they didn't request specific ones (memory allocated cost), we would skip
    calculating the memory cost because we thought it wasn't relevant.  We need to
    check all cost fields to see if they're relevant for the requested fields in the

 app/models/chargeback_rate_detail.rb | 2 +-
 spec/models/chargeback_vm_spec.rb | 11 +
 2 files changed, 12 insertions(+), 1 deletion(-)

Comment 4 Tasos Papaioannou 2018-05-16 18:36:52 UTC
Verified on

Comment 6 errata-xmlrpc 2018-06-25 14:20:46 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.