Hide Forgot
Created attachment 1246039 [details] screen shot of Utilization page Description of problem: ---------------------- Version-Release number of selected component (if applicable): -------------------------------------------------------------- 5.7.1 How reproducible: ---------------- Always Steps to Reproduce: ------------------- 1)Manage a provider.Enable C&U collection for the provider.Wait until at least 2 days worth of C&U data has been captured to see the Utilization charts. 2)Navigate to Optimize->Utilization. 3)Select a provider/cluster/host on the left. Actual results: --------------- The data shown on the right corresponds to Region and doesn't get updated as different item selections are made on the Utilization tree. In the attached screen shot, a host is selected on the Utilization tree, but the data on the right corresponds to CFME Region. Expected results: ----------------- Data on the Optimize->Utilization page should get updated as different item selections are made on the Utilization tree. Additional info: ---------------
https://github.com/ManageIQ/manageiq-ui-classic/pull/324
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/05bed9e5b3ed478ee53da0d3f95152c642b1efc5 commit 05bed9e5b3ed478ee53da0d3f95152c642b1efc5 Author: Dávid Halász <dhalasz@redhat.com> AuthorDate: Wed Feb 8 10:25:44 2017 +0100 Commit: Dávid Halász <dhalasz@redhat.com> CommitDate: Wed Feb 8 10:25:44 2017 +0100 Fixed DOM element names for Utilization & Bottleneck tree select https://bugzilla.redhat.com/show_bug.cgi?id=1417772 https://bugzilla.redhat.com/show_bug.cgi?id=1417774 app/assets/javascripts/miq_tree.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Verified in 5.8.0.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-2017:1367