-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
OCMUI Center Team Sprint 271, OCMUI Center Team Sprint 272
Description:
This was found by Trevor as part of OCMUI-3406. During the HCP wizard, if a user sets the max nodes to be less than min nodes and then later changes a subnet, the validation error goes away even though the number of max node is invalid.
How to reproduce:
- Start the HCP wizard and go to the machine pools step
- Select a VPC and add two subnets
- Click on the Enable autoscaling checkbox
- Set the min nodes to 2 and the max nodes to 1
- Verify the "Max nodes cannot be less than min nodes" error is showing
- Change one of the machine pools to another subnet
- The "Max nodes cannot be less than min nodes" error is no longer showing
See attached video
Expected result
The "Max nodes cannot be less than min nodes" error should always show if the max nodes is less than min nodes.