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

[Machine type] Warning for unsupported machine type is not shown in Review and Create step

    • Product / Portfolio Work
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Center Team Sprint 276, OCMUI Center Team Sprint 277

      Description of problem:

      Warning for unsupported machine type is not shown in Review and Create step for ROSA Classic and ROSA HCP clusters

       

      How reproducible:

      Always

       

      Steps to Reproduce:

      1. Launch cluster creation wizard for ROSA Classic and ROSA HCP cluster
      2. Go through usual creation flow
      3. Choose region us-west-2
      4. Reach Machine pool step
      5. Open machine type list in Compute node instance type section
      6. Turn on toggle to include types that might be unavailable to your account or region
      7. Choose a1.xlarge. There should be warning icon and text next to it
      8. Proceed with next steps as usual
      9. Reach review and create step
      10. See Default machine pool section
      11. Observe Node instance type

       

      Actual results:

      Next to the possibly unavailable machine type (for example: a1.xlarge) is not any warning icon or text for user

       

      Expected results:

      There should be same warning icon and maybe text as in Machine pool step, to make user experience more convenient for creating cluster

        1. Screenshot From 2025-06-04 17-34-50.png
          11 kB
          Aleš Pecha
        2. image-2025-06-04-15-10-25-777.png
          201 kB
          David Aznaurov
        3. Screenshot 2025-06-05 at 11.08.30 AM.png
          259 kB
          Jayakrishnan Mekkattillam

              rh-ee-daznauro David Aznaurov
              apecha-csqe Aleš Pecha
              Aleš Pecha Aleš Pecha
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: