Bug 1372838 - The chargeback report gives wrong information
Summary: The chargeback report gives wrong information
Keywords:
Status: CLOSED DUPLICATE of bug 1346047
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.5.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: 5.7.0
Assignee: Libor Pichler
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 20:53 UTC by Daniel Bello
Modified: 2016-10-03 12:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-09 20:13:35 UTC
Category: ---
Cloudforms Team: Unknown
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Example of the problem. (339.84 KB, application/zip)
2016-09-02 20:53 UTC, Daniel Bello
no flags Details

Description Daniel Bello 2016-09-02 20:53:48 UTC
Created attachment 1197308 [details]
Example of the problem.

Description of problem: I have tried to get the chargeback report from a client in CloudForms 4.0, but i've received a large amount from memory used, storage used, disk i/o used and cpu used, but if you multiply the amount that the report gives by the rates assigned for that user, the result is not the same that i expected. If i've used 8 Ghz in 1 month and the rates for that is $1 USD for 1 month, i've expected that the cost for use is $8 USD, but the report  gave me $0.01 USD. I have the same situation with memory used, disk i/0 used and storage allocated and storage used. I hope that the used item and the cost are right, if i've used 8 GHz in one month and the rates for that is $1 USD for 1 GHZ in month, the cost must give me $8 USD.


Version-Release number of selected component (if applicable):
The appliance is CloudForms 4.0 - CFME 5.5.5.4
RHEL 7.2 x86_64


How reproducible: Set the rates from a customer to 1 and try to get the report of the last month


Steps to Reproduce:
1.Set the rates to 1 by month for each compute/storage ítems and set the rates to the customer by tag.
2. Execute a report of cpu/memory/network/i/o/storage used and compute/storage allocated.
3.Compare the information of the VM vs the report.

Actual results:
The result of the report brings different values than i have expected, for example: If i've used 8 Ghz in 1 month and the rates for that is $1 USD for 1 month, i've expected that the cost for use is $8 USD, but the report  gave me $0.01 USD. (i have the same troubles in the others ítems: storage/memory/etc)


Expected results:
The mount of used and rates should give the correct cost.

Additional info:

Comment 4 Daniel Bello 2016-09-09 12:51:12 UTC
Hi: I have cloned my appliance in CloudForms 4.0. I have registered and upgraded the clone appliance to CloudFOrms 4.1. I have checked the rates and assignments of the chargeback report for the same customer where i try to get the chargeback report. I have run the report of chargeback, but the results is the same than CloudForms 4.0, the report gives me wrong information. I have tried to change the rates for another, but i found that i can't change the period of time, only appears "hourly" option to select.

Comment 5 Colin Arnott 2016-09-09 20:13:35 UTC
Daniel,

This bug appears to be a clone of an existing bug: 1346047

I am going to close this bug as a duplicate, and if there turns out to be something unique about the upgrade process we can work it here or in a new BZ, what ever engineering prefers.

--
Colin Arnott

*** This bug has been marked as a duplicate of bug 1346047 ***

Comment 6 Daniel Bello 2016-10-03 12:44:41 UTC
(In reply to Colin Arnott from comment #5)
> Daniel,
> 
> This bug appears to be a clone of an existing bug: 1346047
> 
> I am going to close this bug as a duplicate, and if there turns out to be
> something unique about the upgrade process we can work it here or in a new
> BZ, what ever engineering prefers.
> 
> --
> Colin Arnott
> 
> *** This bug has been marked as a duplicate of bug 1346047 ***

Ok.


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