-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
XCMSTRAT-589 - [Internal Preview] OCM console can connect to regional OCM instances to manage cluster lifecycle
-
-
-
ACM Console Sprint 261
Description of the Problem
User has opened edit machine pool dialog (either from cluster list or cluster details page) and selected the different machine pool other than the default one. User has now clicked a link (ex: link associated to the ? help tool tip associated to autoscaling) and redirected doc in new tab. User came back to the previous tab and seen that the "Edit machine pool" definition has been reset automatically to default definition. It is wrong behavior and expectation is that Edit machine pool dialog definition should be same as before i.e. before the navigation action.
See the attached recordingsScreencast from 2024-10-24 15-25-56.mp4
This happens with only in the env ?multiregion=true
For non multregion env all looks fine
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging.
- Open a ready ROSA hosted cluster. ( two machine pools named workers-0 and workers-1)
- Click "Actions" menu > "Edit machine pool" context menu.
- Select "workers-1" from machine dropdown.
- Change machine pool definitions like node count or label value.
- Click ? icon associated to "Enable autoscaling".
- Click the doc link and allow the doc definition to load in new tab.
- Go back to previous tab.
- See the "Edit machine pool" definitions.
Actual results:
At Step 9, the "Edit machine pool" dialog definition reset to the default machine pool (i.e. workers-0) although user has selected the machine pool "workers-1" at step 4.
This behavior also clean all the definition change made at step 5 by the user.
Expected results:
At Step 9, the "Edit machine pool" dialog definition should be unchanged i.e the machine pool definition chosen at step 4 should stay on the page.
- is blocked by
-
OCMUI-2467 MultiRegion/RQ Cluster actions => Edit machine pool
- Closed
- mentioned on