-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
1
-
False
-
False
-
None
Description
In a Hypershift ROSA cluster, a machine pool with autoscaling enabled (for ex, minimum, maximum node count is 1). Once the user edit the machine pool i.e. disabled auto scaling ,node count is 2 and saved the changes. The node count wrongly set to 1 instead of 2.
Steps to reproduce:
- Install Hypershift ROSA cluster.( use CLI)
- Wait for installation is successful. (note: there will be machine pool with node count > 2 already)
- Create a machine pool via CLI ($ $ rosa create machinepools --enable-autoscaling --min-replicas=1 --max-replicas=1 --name q1 -c jayam15hypr )
- Launch OCM.
- Locate Hypershift ROSA cluster > Navigate to "Machine pool" tab.
- Click on scale option for the machine pool added in step 3.
- On "Edit node count" dialog ,
- Disable auto-scaling , keep the node count as 2 and click on save.
- View the node count of machine pool after save operation.
Actual results:
After step 8, The node count is set wrongly as 1. It looks like default node count value is not considered while saving the new definitions.
Expected results:
After step 8, The node count should set to 2 .
See the screen capture NodeCountIssue.mp4
- causes
-
HAC-2982 [Hypershift ROSA][Details] Edit node count
- Closed
- mentioned on