Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-4120

[Hypershift ROSA] Wrong compute node calculation or definition from wizard during cluster creation

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

      Description of problem:

      During the creation of ROSA HCP cluster via wizard, under cluster settings > machine pools,
      The user has added three machine pools across different private subnets, Kept the compute node count as 2.  But the cluster creation fails with error 

      Backend error message seems wrong when it is compare inline UI definitions.

      compute node count =2 i.e. 2 >= minimum supported node count for HCP and expectation is that , the node count value mentioned will be added to each machine pool set.
      But it looks like , the  compute node count from UI definition takes as total compute node count and  divided by number of machine pools create each zone/private subnets in backend. This is confusing from UI and forcing user to calculate compute node count manually and set the node count according to total number of machine pools sets.

      Conclusion is that , the user can't keep compute node count(N) if M%N !=0 where M = total count of machine pool set.

      How reproducible:

       Always

      Steps to reproduce:

      1. Launch OCM Staging.
      2. Open ROSA wizard and select control plane type as "Hosted"
      3. Proceed to next steps by providing all required values in each step.
      4. Reach to "Cluster Settings> Machine pools " step.
      5. Select the VPC and add three machine pools for each az/private subnets.
      6. Set the compute node count as 2.
      7. Reach to "Review and create" page and click on "Create cluster".
      8. View the behavior.

      Actual results:

      HCP Cluster creation fails with an error 

      CLUSTERS-MGMT-400: Invalid number of compute nodes: 2. Hosted clusters require that the compute nodes be a multiple of the private subnets 3
      Operation ID: 0e9efa73-eb86-41ee-918a-dcee5bced67b 

      This is confusing while comparing the UI compute node count definitions and total number of machine pool sets.

      Expected results:
      1. Make the compute node count calculation dynamically as per the total number of machine pools sets added/available.
      2. Add a clear note/information on compute node definition to show how compute node  calculation made against the added machine pools.

      Attached recordings ComputeNodeCountHCPIssue.mp4

              kdoberst Kim Doberstein
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Archiver:
              rhn-support-sthamilt Stacey Hamilton
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam

                Created:
                Updated:
                Resolved:
                Archived: