Created attachment 1414341 [details] Screenshot of role failing to update Description of problem: During an initial login as non-admin user with permissions for Settings->Configuration, role name updates are not reflected in the access control accordion until after a manual browser refresh. After the refresh, all role name updates trigger and accordion refresh automatically Version: 5.9.2 How reproducible: 100% so far Steps to Reproduce: 1. Login as admin and user, group and role with minimal user configuration permissions: "Services->Catalog Explorer" and "Settings->Configuration" 2. Login as the non-admin user 3. Navigate to configuration Access Control and create a new role with any set of permissions. 4. Edit the role by changing the name. Example: test-role ==> test-role-edited 5. Repeat steps 3-4 any number of times. Actual results: The updated role name is not reflected in the accordion under Access Control -> CFME Region -> Roles -> <<test-role-edited>>. Additional role creation actions may not display in the accordion but will show up in the role checklist view. A manual refresh will update the accordion and usually allow futures role name updates to refresh the accordion Expected results: Accordion will be refreshed after every role update w/o a manual update Additional info: A manual refresh usually updates resolves the issue for all future role actions
https://github.com/ManageIQ/manageiq-ui-classic/pull/3708
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/631afc7ebb668405d6abbbecbbee4fce99f667a4 commit 631afc7ebb668405d6abbbecbbee4fce99f667a4 Author: Dávid Halász <dhalasz> AuthorDate: Tue Apr 3 04:27:22 2018 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Tue Apr 3 04:27:22 2018 -0400 Force expand active node in TreeBuilder Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1561698 app/presenters/tree_builder.rb | 5 +- 1 file changed, 4 insertions(+), 1 deletion(-)
Verified with 5.10.0.19.
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-2019:0212