Bug 1581724 - chargeback reports based on vms with tags assigned show no records on generation
Summary: chargeback reports based on vms with tags assigned show no records on generation
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: Nandini Chandra
URL:
Whiteboard:
Depends On:
Blocks: 1583786
TreeView+ depends on / blocked
 
Reported: 2018-05-23 13:46 UTC by Felix Dewaleyne
Modified: 2021-09-09 14:12 UTC (History)
5 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1581349 0 high CLOSED [RFE] chargeback rates assigned to tags via multiple tag category assignations do not seem to get saved 2021-12-10 16:12:18 UTC

Description Felix Dewaleyne 2018-05-23 13:46:30 UTC 
Description of problem:
chargeback reports based on vms with tags assigned show no records on generation

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

How reproducible:
all the time

Steps to Reproduce:
1. configure a provider with c&u data collection enabled
2. assign a couple tags from the same category to a couple vms
3. under cloud intel > chargeback > assignments > assignments > compute set chargeback for the category
4. create a chargeback report based on vms
5. generate a report

Actual results:
generated report shows no records

Expected results:
the vms tagged should be displayed

Additional info:
this is all done as admin user
Comment 7 Libor Pichler 2018-05-25 09:19:49 UTC 
*** Bug 1581349 has been marked as a duplicate of this bug. ***
Comment 9 Nandini Chandra 2018-11-15 17:26:21 UTC 
Verified in 5.10.0.23
Note You need to log in before you can comment on or make changes to this bug.