Bug 1595545 - Openstack Storage costs in chargeback is 0.00
Summary: Openstack Storage costs in chargeback is 0.00
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.8.5
Assignee: Libor Pichler
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: 1572700
TreeView+ depends on / blocked
 
Reported: 2018-06-27 06:24 UTC by Niladri Roy
Modified: 2021-12-10 16:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 11:44:08 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Niladri Roy 2018-06-27 06:24:26 UTC
Description of problem:
Storage Used Cost, Storage Allocated Cost, Fixed Storage Cost 1 values are $0.00 in chargeback report

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

How reproducible:
Everytime at Cu env

Steps to Reproduce:
1. 
2.
3.

Actual results:
Storage costs are zero

Expected results:
Storage costs should be non-zero

Additional info:
Provider is Openstack, rate assignment has been done on tenants

Comment 3 Joe Rafaniello 2018-07-31 16:18:38 UTC
Niladri, this sounds very similar to bug #1567254, and fixed in 5.8.4.3, via bug #1576101.  Can you try with 5.8.4.3?

Comment 4 Niladri Roy 2018-08-01 05:51:02 UTC
Hi Joe,

This is doesn't look similar to your mentioned BZ as the report has many columns (not only the Total costs) included and only the storage costs are zero

Please see comment #2 for the reproducer details which has the Cu DB dump and the report name mentioned.

Comment 5 Joe Rafaniello 2018-08-01 14:36:54 UTC
Thanks, I'll take a look.  By the way, with bug #1567254, you only needed one of the required fields excluded from the report for some dependent fields to be empty/0, so the number of fields may or may not be a good indicator.

Comment 13 dmetzger 2018-09-04 11:44:08 UTC
Closing this ticket per the requestors request / comment:

"There was no response from the Cu on my support case related to this BZ.

I went ahead and archived the case today. I think the BZ also can be closed now."


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