-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
-
-
OCMUI Core Sprint 259, OCMUI Core Sprint 260
Description of the Problem
During the debugging the ROSA hosted test failures , it was identified a weired behavior with Minimum node count that was associated to the latest node limit changes.
ROSA Hosted cluster has one machine pool with a node count 10. User tried to add a new machine pool with auto scaling enabled. User has kept the max node value i.e. 240 on both maximum node count as well as minimum node count value. The user has later reduced the minimum node count using minus icon associated to the same. Although the minimum node count limit < max node count limit, the plus icon associated to the field is still disabled.
See the recordings Screencast from 2024-09-18 18-01-44.mp4
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging
- Open a ready ROSA hosted cluster. (assumes the cluster has one machine pool with node count as 10)
- Go to machine pool tab.
- Click add machine pool button.
- Check "Enable autoscaling" option.
- Keep the maximum node count as well as minimum node count value to 240.
- Reduce the minimum node count value to 238 using icon.
- See the behavior of plus icon associated to minimum node count field.
Actual results:
At step 8, The minimum node count value < max node count limit but the plus icon associated to the field is still disabled.
Expected results:
When the minimum/maximum node count field value < max node count limit then the plus icon associated to the fields should be enabled.
- relates to
-
OCMUI-2366 Change HCP max nodes from 51 to 250
- Closed
- mentioned on