Description

Once the user has tried to delete a machine(node) pool(only available node pool)  from a hypershift ROSA cluster, it fails as expected and shows an error message in UI. 

After closing the error message from the machine pool tab section, if a user creates a new machine pool via CLI and tries to delete the same from UI , UI doesn't give an indication that the machine pool is deleted.
The machine pool table didn't refresh the page and deleted the machine pool shown in the UI. If a user tries to delete the machine pool again , it throws the error message. 

Error deleting machine pool

CLUSTERS-MGMT-400: The last NodePool can not be deleted from a cluster.

Operation ID: 2ad39e6b-9312-42dc-9f9a-5721a275b01b

To reflect the machine pool list after delete action the user has to wait for the auto refresh in the cluster details or manually click refresh option.

This creates a lot of confusion and we need to avoid the same. __ 

How reproducible:

 Always

Steps to reproduce:

1. Install Hypershift ROSA via CLI
2. Launch OCM UI staging
3. Once the cluster is ready, go to the machine pools tab.
4. Select the  machine pool(ex: worker) and delete the same.
5. Close the error message shown in the machine pools tab.
6. Create additional machine pools via CLI (ex: rosa create machinepool -c hypf6jaya --name=second-mp --replicas=3)
7. Refresh the machine pool from UI.
8. Select the newly created machine pool and delete the same.
9. See the behavior.
10. Try to delete the newly created machine pool again and view the behavior.

Actual results:

In Step 8, the newly created machine pool is still shown in UI even after the delete action. In step 10, if user tries to delete it again , UI throws the error message wrongly as
CLUSTERS-MGMT-400: The last NodePool can not be deleted from a cluster.

It creates confusion for users.User has to wait for an auto refresh on the cluster page or do a manual refresh to the page to see the updated list.

Expected results:

In Step 10, refresh the machine pool list table as soon as the user completes delete action. This will update the machine pool table as expected and avoid confusions.

Additional info:

Attached screen capture for the same.