-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
False
-
None
-
HAC Infra OCM - Sprint 238
Description of problem:
User has used ROSA wizard for creating a ROSA classic multi-az (availability zone) cluster. After the same action, user launched ROSA wizard again for creating the ROSA Hypershift cluster. The ROSA Hypershift wizard flow shown the wrong definitions around the compute node count. See details below
1. Machine pool step shown the definition as below
It should be compute node count (per machine pool)
2. Review and create step shown the inline definition
Node count calculations are based on zone not as per machine pools.
How reproducible:
Always
Steps to reproduce:
- Launch OCM Staging.
- Open ROSA wizard and select control plane type as "Classic".
- Proceed to next steps by providing all required values in each step(make sure you choose availability as multi-az)
- Create a ROSA classic cluster.
- Open ROSA wizard and select control plane type as "Hosted".
- Reach to machine pool step by providing all required values in each step.
- Select VPC and add two machine pool sets.
- See the behavior of compute node count ( keep the value as 2 ) definitions.
- Proceed to next steps and reach to "Review and create" page.
- Review the definition of compute node count.
Actual results:
Compute node count definition is wrong from both "machine pool" and "review and create" step when user previously used a ROSA wizard for classic multi-az cluster creation.
Expected results:
Compute node definition should be calculated based on the machine pool sets and there should be any leftover definitions from previous wizard steps.