Description of problem: --------------------- Version-Release number of selected component (if applicable): -------------------------- 5.6.0.6 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Generate a chargeback report. 2.Navigate to the Cloud Intel -> Chargeback page. 3.Click reports accordion. Actual results: --------------- Chargebacks reports don't get saved in the 'Saved Chargeback reports' folder in the Reports accordion on the Cloud Intel -> Chargeback page. Expected results: ----------------- Chargebacks reports should get saved in the 'Saved Chargeback reports' folder. Additional info: ---------------- The Chargeback reports do get saved in the 'All saved reports' folder on the Cloud Intel -> Reports page.
https://github.com/ManageIQ/manageiq/pull/8818
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/576d97fa028191feb38f93e61837be85efeca9bc commit 576d97fa028191feb38f93e61837be85efeca9bc Author: lpichler <lpichler> AuthorDate: Thu May 19 12:42:02 2016 +0200 Commit: lpichler <lpichler> CommitDate: Wed May 25 14:15:55 2016 +0200 Fix listing of saved chargeback reports in chargeback section https://bugzilla.redhat.com/show_bug.cgi?id=1336978 Caused after separating chargeback for Vms and containers project in https://github.com/ManageIQ/manageiq/pull/7081 - moved where claused to MiqReportResult - for determing time used format_timezone method - listing only miq_report_results with any miq_report - also query fixed for childs in tree in x_get_tree_custom_kids - query is based in MiqReport#db column instead of MiqReportResult#db - fixed cases for report_results without finished of generation of report - add ordering in trees and content by last_run_on app/controllers/chargeback_controller.rb | 72 ++++++++++------------- app/models/miq_report_result.rb | 13 ++++ app/presenters/tree_builder_chargeback_reports.rb | 19 +++--- 3 files changed, 53 insertions(+), 51 deletions(-)
Verified in 5.6.0.10
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/RHBA-2016:1348