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

[OSD wizard][Private service connect]Do not show "Private service connect" reference or disable private service connect with a note when user select unsupported OCP version i.e. < 4.17

    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 262

      Description of the Problem

      In case user select the OCP version < 4.17 from the wizard step, the cluster privacy section doesn't indicate any information that "Private service connect" doesn't support OCP version < 4.17 . User continued to select the "Use Private service connect" options with cluster privacy as private without any issue in wizard. The wizard only blocked at the time of cluster submission with a inflight error from backend. This is late in the cluster creation flow from UI and need to change.

      The expectation could be 

      1. Do not show any private service connect references from wizard (Cluster privacy > Use private service connect)  in case user choose the version < 4.17 (or any unsupported version) OR
      2. Disable all the private service connect reference in wizard  (Cluster privacy > Use private service connect) with a note indicate that the OCP version >= 4.17 needed to enable or use the feature.

      How reproducible:

      always

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Open a OSD wizard flow( GCP cloud with CCS).
      3. Select the OCP version < 4.17 from version drop-down from Cluster settings > detail step.
      4. Proceed to next steps.
      5. Reach cluster privacy step and select the privacy as "private".
      6. Select both "install into existing VPC" and "Use private service connect".
      7. Proceed to next steps with required definitions.
      8. Reach "review and create" step and click "Create cluster" button
      9. See the behavior.

      Actual results:

      Cluster submission at step 8 has been blocked with a backend error stating as below.

      Error seems to be related inflight check from backend due to unsupported versions and it is late in the OCM UI cluster submission cycle.

      Expected results:

      In case of unsupported version selection in wizard , then 

      1. Do not show any private service connect references from wizard (Cluster privacy > Use private service connect)  in case user choose the version < 4.17 (or any unsupported version) OR
      2. Disable all the private service connect reference in wizard  (Cluster privacy > Use private service connect) with a note indicate that the OCP version >= 4.17 needed to enable or use the feature.

              zherman Zac Herman
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: