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

[ROSA V2 'classic' wizard]Missing validation when same availability zone selected Virtual Private Cloud (VPC) subnet settings

    • False
    • Hide

      None

      Show
      None
    • False
    • OCM Core Sprint 253

      Description of problem:

      In ROSA Wizard v2 flow, under "Network configuration" > Virtual Private Cloud (VPC)  step, if user wrongly selected the same availability zone value for the multiple private subnet definition then there is no validation thrown for the user. This is wrong.

      Screenshot from V2 wizard

      Screenshot from V1 wizard

      How reproducible:

      always

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Launch https://console.dev.redhat.com/openshift/create/rosa/wizard?rosaV2=true 
      3. Fill all required fields from each step and reach to "Cluster settings > Details" step.
      4. Select availability zone as "multi-zone".
      5. Fill all required fields from each step and reach to "Networking> Configuration" step.
      6. Select the cluster privacy as "private".
      7. Click "Next" button and select a VPC (make sure you choose a VPC configured with more than two AZs)
      8. Select same availability zone in the drop-down field (including private subnet).
      9. Click "Next" and see the validations against the fields.

      Actual results:

      At Step 9, The validation when user chooses same AZs in required drop-down field is missing from rosa v2 flow. The same seen well in Rosa v1 wizard.

      Expected results:

      At Step 9, The validation message  should throw in the field when user chooses same AZs in required drop-down field in Rosa v2 flow. 

            dtaylor@redhat.com David Taylor
            jmekkatt@redhat.com Jayakrishnan Mekkattillam
            Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: