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

[ROSA Wizard v2] "Review and create" page wrongly indicated the "Custom KMS key ARN" although user selection was "Use default KMS Keys".

    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      In ROSA Wizard v2 flow, In "Cluster settings > Details> Advanced encryption" section , user has selected "use custom KMS key"  radio and input some ARN definition in the field. later user has changed back to "Use default KMS key" by selecting the respective radio. Once user reached to "Create and review" step, the page shown the "Custom KMS key ARN" value wrongly although it indicate that "Encrypt volumes with customer keys" is disabled.

      Attached screen recordings LeftoversCustomKeyArnsInReviewStep.mp4

       

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Launch https://console.dev.redhat.com/openshift/create/rosa/wizard?rosaV2=true 
      3. Reach to "Cluster settings > Details" step.
      4. Expand the "Advanced encryption" section.
      5. Select the "use custom KMS key" radio and fill Key ARN field
      6. Select the "use default KMS key" radio.
      7. Fill all required fields  and Click "Next".
      8. Fill all required fields from each step and reach to "Review and create" step.
      9. See the property definition under cluster settings section.

      Actual results:

      At Step 9, Under cluster settings section, the property "Custom KMS key ARN" seen wrongly although user has selected "use default KMS key" in Step 6.

      Expected results:

      At Step 9, Under cluster settings section, the property "Custom KMS key ARN" shouldn't be shown as the  users selection is "use default KMS key" in Step 6.

              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: