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

[OSD Wizard][GCP]Unable to select existing VPCs from drop-down under VPC Settings in GCP wizard flow.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • Core UI
    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      In OSD (CCS) GCP wizard flow, User is unable to select the existing VPC name from the drop-down under networking > VPC settings page. After selection of VPC name from the drop-down the selected value is not preserved.

      Refer attached recordings ExistingVPCNameDropdownIssueGCP.mp4

      The behavior works fine in prod not in staging.

      Steps to reproduce:

      1. Launch OCM Staging UI.
      2. Open OSD wizard.
      3. Select subscription as "Annual fixed capacity subscription" and Infrastructure type as "Customer cloud subscription"
      4. Click "Next" and choose cloud provider as GCP.
      5. Proceed to "Next" steps and reach to "Networking"> "Configuration".
      6. Enable the checkbox "Install into an existing VPC" and click "Next".
      7. Click on "Existing VPC name" drop-down and select the VPC value.
      8. See the behavior.

      Actual results:

      At Step 7,  After selection of VPC name from the drop-down the selected value is not preserved. Hence user is unable to select the existing VPC name from the drop-down.

      Expected results:

      At Step 7,  The  selection of VPC name from the drop-down should be successful and after selection the value should be preserved

      This was happening across all the browsers and tested with chrome, edge and firefox.

              rh-ee-camadorg Celia Amador Gonzalez
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: