Red Hat Bugzilla – Bug 1322153
Wrong link in breadcrumb trail while viewing bottleneck events
Last modified: 2016-06-29 11:45:58 EDT
Description of problem: ----------------------- Version-Release number of selected component (if applicable): -------------------------- 5.5.3.2 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Generate bottleneck events for an infra provider.View the bottleneck events for the provider by navigating to Optimize->Bottlenecks page. 2.Click any of the host or cluster Bottleneck events.In the (cluster)event bubble, click the 'cluster' link. This takes you to the cluster summary page.In the breadcrumb trail, click 'Activity'.This takes you back to the Bottleneck summary page. 3.Repeat step 2 and once on the cluster summary page, notice that the breadcrumb trail has the 'Clusters' link instead of the 'Activity' link. Actual results: --------------- Wrong link in breadcrumb trail while viewing bottleneck events Expected results: ----------------- Correct link in breadcrumb trail while viewing bottleneck events Additional info: ----------------
https://github.com/ManageIQ/manageiq/pull/8355
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/0f8498f7540dfa1a8d2dcfdeaf9dbe59e8b98516 commit 0f8498f7540dfa1a8d2dcfdeaf9dbe59e8b98516 Author: Zita Nemeckova <znemecko@redhat.com> AuthorDate: Fri Apr 29 16:51:09 2016 +0200 Commit: Zita Nemeckova <znemecko@redhat.com> CommitDate: Mon May 2 14:23:55 2016 +0200 Correct breadcrumb in Cluster (Summary) https://bugzilla.redhat.com/show_bug.cgi?id=1322153 app/controllers/miq_capacity_controller.rb | 6 ++---- spec/controllers/miq_capacity_controller_spec.rb | 16 ++++++++++++++++ 2 files changed, 18 insertions(+), 4 deletions(-)
Verified in 5.6.0.6
https://github.com/ManageIQ/manageiq/pull/8473
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