Bug 1574906 - chargeback report showing monthly cost for instances which got deleted after 1 day
Summary: chargeback report showing monthly cost for instances which got deleted after ...
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
urgent
urgent
Target Milestone: GA
: cfme-future
Assignee: Libor Pichler
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-04 10:07 UTC by Niladri Roy
Modified: 2021-06-10 16:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-30 13:26:30 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Niladri Roy 2018-05-04 10:07:29 UTC
Description of problem:
- An instance was created, and then removed after some time.

- Another instance, with the same name, but different vCPU and memory allocations, were created.

- A chargeback report was created.  When it is run, only the older instance is charged monthly, whereas the newer instance doesn't show in the monthly report at all.

- All reports regarding daily, weekly, and this current month work (show both instances), however, when we do multi-monthly reports (reports for instances newly created and removed both or for current month and last month) we get the above scenario where only the removed instance shows.

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

How reproducible:
Always 

Steps to Reproduce:


Actual results:
instance removed gets charged with monthly billing

Expected results:
instance created should get charged with monthly billing and instance removed should get charged with daily billing (supposed it was terminated after 1 day...so only 1 day billing should be done)

Additional info:


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