-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
-
-
OCM UI Sprint 245, OCM UI Sprint 246
Description of problem:
The "Edit machine pool" dialog loads the definition of previously opened machine pool definition from different cluster and create bad functional experience to the user.
- User opens "Edit machine pool" from of one of the cluster (say cluster-1) and make changes to the definition and saved the changes.
- User opens "Edit machine pool" from of another cluster (say cluster-2) but the previously changed machine pool definition (cluster 1) seen in "Edit machine pool". Due to this some cases the compute node count reported as disabled with insufficient quota.
Please find recording EditMAchinePoolPreviousClusterMpsIssue.mp4
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging.
- Select a ready OSD cluster.
- Click on "Edit machine pool" context menu.
- Save the definition after changing the node count value.
- Select a ready Hypershift cluster.
- Click on "Edit machine pool" context menu.
- View the behavior.
Actual results:
At Step 7, The previously changed machine pool (At step 4) definition from different cluster loaded wrongly to the "Edit machine pool" definition of new cluster.
Expected results:
"Edit machine pool" definition should be loaded always the definition of selected cluster. There shouldn't be any effect of previously loaded "Edit machine pool" definitions.
- is triggered by
-
HAC-5346 [OCM UI]Machine pool changes from Edit machine pools didn't reflect in machine pool table immediately after save action.
-
- Closed
-
- mentioned on