Red Hat Bugzilla – Bug 1552817
SUI doesn't display costs for SCVMM services
Last modified: 2018-05-07 16:44:34 EDT
New commit detected on ManageIQ/manageiq/gaprindashvili: https://github.com/ManageIQ/manageiq/commit/a75d746056af0084ca84fd55209d5119f1e29f46 commit a75d746056af0084ca84fd55209d5119f1e29f46 Author: Gregg Tanzillo <gtanzill@redhat.com> AuthorDate: Mon Mar 5 15:51:11 2018 -0500 Commit: Gregg Tanzillo <gtanzill@redhat.com> CommitDate: Mon Mar 5 15:51:11 2018 -0500 Merge pull request #17082 from lpichler/fix_service_uniqueness Add uniqueness of service for generation chargeback report for SSUI (cherry picked from commit c2f76b64e346123c343e1c58fbcaa3d97260ce44) https://bugzilla.redhat.com/show_bug.cgi?id=1552817 app/models/service.rb | 4 +- spec/models/service_spec.rb | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
verified that service id is used to distinguish between services of the same name while generating service chargeback reports for the services. [root@dhcp-8-196 log]# zgrep Chargeback-Vm-Monthly * | more evm.log-20180413.gz:[----] I, [2018-04-12T20:02:44.217541 #12023:de9108] INFO -- : MIQ(MiqReport#build_create_results) Creating report results with hash: [{:name=>"Chargeback-Vm-Monthly-cat-item-1", :userid=>"s ystem", :report_source=>"Daily scheduler", :db=>"ChargebackVm", :last_run_on=>2018-04-13 00:02:44 UTC, :last_accessed_on=>2018-04-13 00:02:44 UTC, :miq_report_id=>nil, :miq_group_id=>nil}] evm.log-20180413.gz:[----] I, [2018-04-12T20:02:44.314215 #12023:de9108] INFO -- : MIQ(Service#generate_chargeback_report) Report Chargeback-Vm-Monthly-cat-item-1 generated evm.log-20180413.gz:[----] I, [2018-04-12T20:02:44.719621 #12023:de9108] INFO -- : MIQ(MiqReport#build_create_results) Creating report results with hash: [{:name=>"Chargeback-Vm-Monthly-cat-item-2", :userid=>"s ystem", :report_source=>"Daily scheduler", :db=>"ChargebackVm", :last_run_on=>2018-04-13 00:02:44 UTC, :last_accessed_on=>2018-04-13 00:02:44 UTC, :miq_report_id=>nil, :miq_group_id=>nil}]
verified in 5.9.2.2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1328