-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
None
Description of problem:
For a fresh ROSA / OSD cluster, the machine pool contains the default name as worker. User has created a new machine pool for the same cluster. User has also updated the taint definition for the worker node. After this step the context menus "Edit taint" and "Delete" options are disabled for the newly created machine pool. The tool tip text shown as "Default machine pool can't be deleted" and "Default machine pool can't have taints" .This is wrong indication could create confusions and need a fix.
See recordings attached -DefaultMPvsNewlyAddedMPContextMenus.mp4
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging.
- Open an ROSA/ OSD cluster and go to machine pool tab.
- Create a new machine pool with name "mp1".
- Update the machine pool "worker" with taint definition.
- See the context menu definitions for machine pool "mp1"
Actual results:
At step 5, Both delete and edit taint context menus are disabled for "mp1" and it was indicated that in tool tip text "Default machine pool can't be deleted" and "Default machine pool can't have taints". It create confusions as the machine pool "mp1" was added by the user and not the default one.
Expected results:
At step 5, Need a better presentation in context menus against the machine pools to avoid mentioned confusions as the machine pool is not the default one.
- relates to
-
HAC-3801 Add Support for delete/modify the Default machine pool from ROSA UI
- Closed
- mentioned on