Bug 1559807 - openstack chargeback based on chargeback per vm does not show storage costs by storage types correctly
Summary: openstack chargeback based on chargeback per vm does not show storage costs b...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.9.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.10.0
Assignee: Libor Pichler
QA Contact: Danylo Kholodov
URL:
Whiteboard:
Depends On:
Blocks: 1578394
TreeView+ depends on / blocked
 
Reported: 2018-03-23 10:18 UTC by Felix Dewaleyne
Modified: 2021-09-09 13:30 UTC (History)
5 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1578394 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:02:10 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
tags_category (139.47 KB, image/png)
2018-11-27 10:38 UTC, Danylo Kholodov
no flags Details

Description Felix Dewaleyne 2018-03-23 10:18:23 UTC
Description of problem:
when generating chargeback reports against openshift based on "chargeback per vm", storage costs are not included

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

How reproducible:
all the time (customre environment)

Steps to Reproduce:
1. set in openshift two cloud volues, one of type SSD and one of standard type
2. create tags for the storage types in CloudForms ; assign them to storages in cloudforms
3. create a new chargeback rate for each type, each at a different cost
4. create report on all the storage costs columns and chargeback rate for the vm

Actual results:
when reports are generated Cloudforms sees no storage

Expected results:
the costs are computed correctly

Additional info:
customer data will be attached (pdf describing in more details their steps)

Comment 8 Danylo Kholodov 2018-11-27 10:38:38 UTC
Created attachment 1508794 [details]
tags_category

Comment 11 Danylo Kholodov 2019-01-09 10:55:30 UTC
Verified at CFME 5.10.0.29


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