Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2824

[Cluster details]Error message wrongly preserved in the page even after clearing the error cause in "cluster roles and access" page

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • A-Team
    • ACM Console Sprint 265

      Description of the Problem

      OCM UI page has thrown an error message in the respective dialog when the user tried to add duplicated users from the "cluster roles and access " section. But the error message has not been cleared from the page even after the error reason has cleared or solved. It requires an explicit refresh of the cluster details to clean those error messages and it looks wrong.

      See attached recording Screen Recording 2025-01-02 at 3.04.45 PM.mov

      Note: The issue appears only on staging not in production env. Hence suspecting that it could be regression issue on recent multiregion MR merges.

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging
      2. Open a ready cluster (ex: ROSA classic).
      3. Go to "Access control" tab.
      4. Click "Cluster roles and access" then click "Add user" button.
      5. Fill the user id as "test" and select the group radio "dedicated-admins".
      6. Click "Add user".
      7. Repeat step 4 to 6 .
      8. Click "Cancel" button once you see the error message on the dialog.
      9. See the error message banner in the page.

      Actual results:

      At step 9, the error message banner from UI has not cleared until user refresh the cluster details page.

      Expected results:

      At step 9, the error message banner from UI should be cleared once user click "Cancel" button at step 8.

              rh-ee-daznauro David Aznaurov
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: