Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-40444

Display of role (remediations user) and member groups for role is displaying incorrectly and causes errors

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None
    • Access & Management Sprint 113, Access & Management Sprint 114

      I have an account I have been using for RBAC rhel role testing and as such I have removed  items from the "default access" group. The group is now "custom access group".

      When I look at the groups (User access > Groups view) and click on the "Custom default access"  there is no "remediations user" role displayed. If I look at the roles (User access > Roles view) I do see a "remediations user" role. On the "remediations user" row there is "1" displayed for groups.  Clicking on the "1" displays an inline row showing the role as belonging to "Default access" group. 

      Clicking on the "Default access" link here causes errors to be displayed and no items populated in the results table. Clicking on the other tabs in the table (Members, Service accounts) also displays errors. I have added screenshots of these labels.

      I had removed all remediations roles from the access groups. The remediations permissions are now included via the new rhel roles (rhel admin, thel operator, and rhel viewer) by including the rhel roles in new groups and adding members to these new groups. I say this just for some context.

       

       

        1. def_access_error_ from 2025-06-04 13-55-39.png
          115 kB
          PJ Richardson
        2. members_error_rbac 2025-06-04 14-05-26.png
          38 kB
          PJ Richardson
        3. rem_user_role_2025-06-04 13-52-41.png
          80 kB
          PJ Richardson
        4. rem_user_role_two_ 2025-06-04 13-54-17.png
          111 kB
          PJ Richardson

              rh-ee-zhzeng Jay Zeng
              prichard@redhat.com PJ Richardson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: