Red Hat Bugzilla – Bug 1417774
Data on the Optimize->Bottlenecks page doesn't get updated as different item selections are made on the Bottlenecks tree
Last modified: 2017-05-31 10:33:43 EDT
Description of problem: ----------------------- Data on the Optimize->Bottlenecks page doesn't get updated as different item selections are made on the Bottlenecks tree. This could be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1417772 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.Generate bottleneck events for the provider. 2)Navigate to Optimize->Bottleencks. 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 Bottlenecks tree. Expected results: ----------------- Data on the Optimize->Bottlenecks page should get updated as different item selections are made on the Bottlenecks 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.3
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