Description of problem: When a condition is created in CFME, the browser will navigate to the details of the condition. However, the accordion displays that we are in the "All Conditions" page. I have not seen such behavior with the other control objects (alerts, policies, etc.). When these objects are created, the browser navigates to the details of the object and the accordion reflects that the user is on the detail page. I noticed that this is present in both CFME 5.9.9 and CFME 5.10.2 Version-Release number of selected component (if applicable): 5.9.9 and 5.10.2 How reproducible: 100% Steps to Reproduce: 1. Create a condition 2. Look at accordion 3. Actual results: The "All Conditions" field in the accordion is highlighted, Expected results: The condition in the accordion should be highlighted. Additional info: This is blocking automated testing.
NOTE, this only affects the following condition classes: [Replicator, Pod, Container Node, Container Image, Container Project, Provider, Physical Infrastructure]
Created attachment 1539486 [details] incorrect object highlighted in accordion
Created attachment 1539490 [details] expected results - object itself is highlighted (alerts)
fixing https://github.com/ManageIQ/manageiq-ui-classic/pull/5302
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/e8f4580fc1d21564cb497c68cafca9cd82db4977 commit e8f4580fc1d21564cb497c68cafca9cd82db4977 Author: Hilda Stastna <hstastna> AuthorDate: Mon Mar 4 10:09:19 2019 -0500 Commit: Hilda Stastna <hstastna> CommitDate: Mon Mar 4 10:09:19 2019 -0500 Fix highlighting the condition in accordion after creating it Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1683697 app/controllers/miq_policy_controller/conditions.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 1698400 has been marked as a duplicate of this bug. ***
I am seeing a similar issue in editing a condition, page displayed is the details page for the condition, but the accordion is highlighting the class of the condition. I will right a separate BZ for this however, since this BZ is specific to condition creation. With that in mind, this BZ is verified in 5.11.0.1.20190424210327_58b5dbd. Steps of verification: 1) Create conditions in each of the available classes 2) After each condition creation, verify that the condition description is properly highlighted in the accordion. And that we are in fact on the details page for the condition. I will link the new BZ once it is written.
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-2019:4199