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

[Data sovereignty] User's approval (acknowledgement) for Y stream update(Update strategy : Recurring update) for a cluster has failed.

XMLWordPrintable

    • ACM Console Sprint 265

      Description of the Problem
      User has tried to provide acknowledgement for Y stream( ex: 4.16.28 to 4.17.11) update has failed from OCMUI.

      In OCM UI staging, User has opened a ROSA classic (or ROSA hosted) cluster that require to update the Y stream version update. As a first step, user went to settings tab of the cluster and a banner indicated for an administrator acknowledgement prior to the upgrade. User tried to provide the acknowledgement and proceed to next steps but the approval dialog indicated the action has failed.
      The same procedure was tried with production code and worked without any issue.
      It looks like some difference in the backend API call method in multiregion enabled staging env vs production env.
      Please refer the recorded video on both staging vs production behavior.Screen Recording 2025-01-16 at 2.42.22 PM.mov

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging
      2. Install  a ROSA classic or hosted cluster with version 4.16.28 ( or any version that allow Y stream update).
        1. Make sure cluster set the update strategy set to "Recurring updates" during the installation.
      3. Once cluster is ready, Go to settings tab.
      4. Click "Provide approval" link under "administrator acknowledgement" banner.
      5. Type "Acknowledge" in the input field from the model.
      6. Click the button "Approve and continue".
      7. See the behavior.

      Actual results:

      At step 7, The user approval action has failed and reported error in UI as mentioned in attached recording.

      Expected results:

      At step 7, The user approval action should be successful from the UI 

        1. Screen Recording 2025-01-16 at 2.42.22 PM.mov
          45.07 MB
        2. Screen Recording 2025-01-20 at 3.05.20 PM.mov
          31.41 MB

            [OCMUI-2941] [Data sovereignty] User's approval (acknowledgement) for Y stream update(Update strategy : Recurring update) for a cluster has failed.

            Jayakrishnan Mekkattillam added a comment -

            Verified the changes in staging today. Fix working as expected and user could able to create or submit the approval for a ROSA hosted cluster Y stream update when recurring update strategy set.  Following areas are covered during the tests and please find them below

            For a ROSA classic and ROSA hosted cluster (non regionalized) - Recurring update strategy was set and user was successfully able to provide administrator approval for a Y stream update

            1. Update via a click action on "Provide approval" button placed in right pane in settings tab was succeeded
            2. Update via a click action on "Provide approval" link from settings tab banner was succeeded

            Note : The test coverage didn't include the regionalized cluster behavior with recurring updates. Thanks

            Jayakrishnan Mekkattillam added a comment - Verified the changes in staging today. Fix working as expected and user could able to create or submit the approval for a ROSA hosted cluster Y stream update when recurring update strategy set.  Following areas are covered during the tests and please find them below For a ROSA classic and ROSA hosted cluster (non regionalized) - Recurring update strategy was set and user was successfully able to provide administrator approval for a Y stream update Update via a click action on "Provide approval" button placed in right pane in settings tab was succeeded Update via a click action on "Provide approval" link from settings tab banner was succeeded Note : The test coverage didn't include the regionalized cluster behavior with recurring updates. Thanks

            David Aznaurov added a comment -

            jmekkatt@redhat.com I will add my discussions with backend folks as well. https://redhat-internal.slack.com/archives/C04HAERGV19/p1737390656232139

            David Aznaurov added a comment - jmekkatt@redhat.com I will add my discussions with backend folks as well. https://redhat-internal.slack.com/archives/C04HAERGV19/p1737390656232139

            Jayakrishnan Mekkattillam added a comment - - edited

            OCM-13556 is blocker for upgrade in staging and blocking the testing of current change in this ticket too.
            cc : rh-ee-daznauro kdoberst FYI.

            Jayakrishnan Mekkattillam added a comment - - edited OCM-13556 is blocker for upgrade in staging and blocking the testing of current change in this ticket too. cc : rh-ee-daznauro kdoberst FYI.

            Jayakrishnan Mekkattillam added a comment -

            Currently we are unable to provide a successful approval or acknowledgement from a cluster in staging env. It looks like the issue with backend. Following up in slack converstation https://redhat-internal.slack.com/archives/CB53T9ZHQ/p1737530530455179
            This blocks the issue verification from OCM UI side. Thanks 

            Jayakrishnan Mekkattillam added a comment - Currently we are unable to provide a successful approval or acknowledgement from a cluster in staging env. It looks like the issue with backend. Following up in slack converstation https://redhat-internal.slack.com/archives/CB53T9ZHQ/p1737530530455179 This blocks the issue verification from OCM UI side. Thanks 

            David Aznaurov added a comment -

            Hi jmekkatt@redhat.com,

            1. Fixed PR is being reviewed.
            2. For regionalized clusters after investigation it comes up that the bug is on the backend side (version_gates are not being returned by the API call). Backend folks have been notified. Whenever backend fixes issue, there will be no bug, since the call is being made to the correct API endpoint and everything works for HCP (global) it should work for HCP (regionalized) as well.

            I guess after PR merged and it works for HCP(global) and ROSA classic clusters we will have to remove it from multi region block.

            WDYT kdoberst 

            David Aznaurov added a comment - Hi jmekkatt@redhat.com , Fixed PR is being reviewed. For regionalized clusters after investigation it comes up that the bug is on the backend side (version_gates are not being returned by the API call). Backend folks have been notified. Whenever backend fixes issue, there will be no bug, since the call is being made to the correct API endpoint and everything works for HCP (global) it should work for HCP (regionalized) as well. I guess after PR merged and it works for HCP(global) and ROSA classic clusters we will have to remove it from multi region block. WDYT kdoberst  

            Jayakrishnan Mekkattillam added a comment - - edited

            Hi rh-ee-daznauro , I have tested above mentioned scenarios against staging env today.

            Following are findings.

            1. On ROSA classic and ROSA hosted cluster (non regionalized) - Recurring update strategy was set and user was able to provide administrator approval partially for a Y stream update as mentioned below. 
              1. Update via a click action on "Provide approval" button placed in right pane in settings tab fails with backend error `Upgrade policies are not supported for this cluster`
              2. Update via a click action on "Provide approval" link from settings tab banner was succeeded
            2.  On ROSA hosted cluster regionalized cluster - Recurring update strategy was set and user was unable to provide administrator approval for a Y stream update and fails with different backend errors as reported below 
              1. Update via a click action on "Provide approval" button placed in right pane in settings tab fails with backend error `Upgrade policies are not supported for this cluster`   
              2. Update via a click action on "Provide approval" link from settings tab banner fails with backend error `Version gate 'f721546f-6f9d-11ef-9a77-0a580a81089a' not found`
              3. Interestingly couple of above situation report different errors and please see attached recording Screen Recording 2025-01-16 at 2.42.22 PM.mov
              4. Note : Issue happens only with recurring update. The individual update allowed to provide acknowledgement and user was able to schedule the update successfully

            Could you please take a look? Thanks.

            Jayakrishnan Mekkattillam added a comment - - edited Hi rh-ee-daznauro , I have tested above mentioned scenarios against staging env today. Following are findings. On ROSA classic and ROSA hosted cluster (non regionalized) - Recurring update strategy was set and user was able to provide administrator approval partially for a Y stream update as mentioned below.  Update via a click action on "Provide approval" button placed in right pane in settings tab fails with backend error `Upgrade policies are not supported for this cluster` Update via a click action on "Provide approval" link from settings tab banner was succeeded  On ROSA hosted cluster regionalized cluster - Recurring update strategy was set and user was unable to provide administrator approval for a Y stream update and fails with different backend errors as reported below  Update via a click action on "Provide approval" button placed in right pane in settings tab fails with backend error `Upgrade policies are not supported for this cluster`    Update via a click action on "Provide approval" link from settings tab banner fails with backend error `Version gate 'f721546f-6f9d-11ef-9a77-0a580a81089a' not found` Interestingly couple of above situation report different errors and please see attached recording Screen Recording 2025-01-16 at 2.42.22 PM.mov Note : Issue happens only with recurring update. The individual update allowed to provide acknowledgement and user was able to schedule the update successfully Could you please take a look? Thanks.

            Jayakrishnan Mekkattillam added a comment -

            kdoberst rh-ee-dcooper  Could you please take a look? Thanks

            Jayakrishnan Mekkattillam added a comment - kdoberst rh-ee-dcooper   Could you please take a look? Thanks

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

                Created:
                Updated:
                Resolved: