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

[OCMUI][OSD wizard] WIF config id retained in wizard when the selected wif config was deleted from background.

    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 260, OCMUI Core Sprint 261

      Description of problem:

      Once user select the WIF config id from OSD wizard flow and meanwhile the wif config was removed from backend then even after refresh action against WIF config field, the deleted WIF config ID was wrongly retained in the field. This is wrong behavior. If the selected wif config doesn't exists after refresh then it needs to ask user to select the wif config. There should not be any reference of deleted wif config.

      please refer attached recording Screencast from 2024-09-25 11-55-30.mp4

      How reproducible:

      Always

      Steps to Reproduce:

      1. Launch OCM UI staging.
      2. Open OSD wizard.
      3. In billing mode step, Select "Subscription type" as "Annual: Fixed capacity subscription from Red Hat".
      4. In billing mode step, Select "infrastructure type" as "Customer cloud subscription".
      5. Click next and  select cloud  provider as google.
      6. Select authentication type as WIF.
      7. Select a WIF config.
      8. Delete the WIF config i.e. use CLI command to delete the wif config.
      9. Go back to wizard and keep refreshing the WIF config.
      10. See the behavior.

      Actual results:

      At step 9, The wif config id wrongly retained in the WIF field once it deleted from the backend even after refresh.

      Expected results:

      At step 9, The wif config field should be cleared with deleted wif config references once its is removed from backend. The API responded correctly with available wif config during refresh action.

              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: