-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
OCMUI Center Team Sprint 271, OCMUI Center Team Sprint 272
Description of problem:
The Maximum nodes per machine pool value is not reset to the default based on the machine pool definitions. In the Machine Pool step of the ROSA hosted wizard, the user initially added three machine pools and set both the Minimum nodes per machine pool and Maximum nodes per machine pool values to 1. The user then removed a couple of machine pools, which resulted in the Minimum nodes per machine pool value resetting to 2. However, the Maximum nodes per machine pool value remained at 1, which eventually triggered a validation error. The expected behavior is that the Maximum nodes per machine pool value should also reset to 2, in accordance with the updated machine pool definition
See the recording.Screen Recording 2025-05-08 at 11.39.30 AM.mov![]()
How reproducible:
always
Steps to Reproduce:
- Go to OCM UI staging
- Launch ROSA wizard.
- Select control plane as "Hosted" and proceed to next steps.
- In machine pool step, select a VPC.
- Add three machine pools subnet definitions.
- Select "Enable autoscaling" checkbox.
- Set the Minimum nodes per machine pool and Maximum nodes per machine pool values to 1.
- Remove the couple of machine pools added at step 5 using
icon - Review the Minimum nodes per machine pool and Maximum nodes per machine pool values.
Actual results:
The Minimum nodes per machine pool value was reset to 2, but the Maximum nodes per machine pool value was not updated and remained at 1. This resulted in a validation error in the wizard.
Expected results:
Both the Minimum nodes per machine pool and Maximum nodes per machine pool values should be reset to 2, which is the minimum node count defined for HCP.