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

[OCMUI] [OSD GCP with WIF ]The wrong version selected by default when user switches the OSD authentication type from "Service account" to "Workload identity federation"

    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 259

      Description of the Problem

      Launched OSD wizard and chosen cloud provider as GCP with authentication type as service account. Proceed to Cluster settings > details step. Selected a  version i.e. < 4.17 ex : 4.14 from the dropdown.  User went back to billing step and changed the authentication type as workload identity federation. Reached again Cluster settings > details step. The default version selected seems wrong as WIF only supported version > 4.17 
      See the recording added  Screencast from 2024-09-18 18-42-22.mp4

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging 
      2. Open OSD wizard.
      3. Choose cloud provider as Google cloud and authentication type as "Service account".
      4. Reach to cluster settings > details step.
      5. Select a version < 4.17 ex: 4.14.
      6. Click "back" button.
      7. Select the authentication type as "WIF" and fill valid WIF config ids.
      8. Click "Next" button.
      9. See the version field behavior,{}

      Actual results:

      At step 9, The default version value shown wrong and doesn't satisfy the condition of WIF supported OCP version i.e. > 4.17 

      Expected results:

      At step 9, The default version value should be cleared from the field if the version doesn't  satisfy the condition of WIF supported OCP version i.e. > 4.17

              robertoemanuel Roberto Emanuel
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: