-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
False
-
None
Description of problem:
Created a OSD GCP cluster, the machine pool contains the default name as worker. User has created a new machine pool for the same cluster and during the creation of machine pool, updated the taint definitions. After successful creation of machine pool, both machine pools i.e. the default worker machine pool and the newly added machine pool context menu options like delete and edit taint are disabled.
See the recordings - DefaultMPsNewMPsOSDGCPIssue.mp4
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging.
- Open OSD cluster and go to machine pool tab.
- Create a new machine pool with name "mp1" (specify the taint definition)
- See the context menu definitions for machine pool "mp1" and "worker".
Actual results:
At step 4, Both delete and edit taint context menus are disabled for newly added machine pool( "mp1" ) as well as for "worker" nodes. This is wrong behavior.
Expected results:
At step 4, The delete and edit taint context menus should be enabled for newly added machine pool i.e. "mp1" in this case
- relates to
-
HAC-3801 Add Support for delete/modify the Default machine pool from ROSA UI
-
- Closed
-
- mentioned on