-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
Description of problem:
In HCP cluster wizard, if the user tries to add a machine pools with autoscaling enabled and mention the maximum node count value exceeds the support limit count then there was no field validation thrown. The Submission action fails with backend error. This was seen with "Add machine pool" dialog.
Ex: Sum total of machine pool node count in cluster is Min: 4 Max: 7 with auto-scaling enabled. But user allowed to set the node count as 50 which is wrong and no validation in place. The maximum node count supported in this case should be 51 - 7 = 44
see the recording attached AddMachinePoolWrongCountCalculation.mp4
How reproducible:
always
Steps to Reproduce:
- Launch OCM UI staging.
- Go to a ready ROSA HCP cluster.
- Go to machine pool tab.
- Click "Add machine pool" button.
- Set the maximum nodes to 50. (or <51 and > 51-N where N will be sum of node count across all machine pool)
- Click "Add machine pool" button.
- See the behavior.
Actual results:
There was no validation error thrown against the maximum node count field when the specified count greater than supported limits. The error reported from backend when submitting the machine pool data.
Expected results:
Do not show unsupported node count values in compute node count definitions.
Throw validation error against maximum node count when the limit exceeds the allowed limit.
- blocks
-
OCMUI-1025 Creating a node pol on a HCP cluster - Enforce maximum 60 node limit across a cluster
- Closed
- is related to
-
OCMUI-1190 OCM UI Regression tests (in Staging) - Sprint 245
- Closed
- mentioned on