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. 

Danger alert:Error deleting machine pool

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

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

The user has closed the error message and went back to cluster details i.e machine pools tab.

The error message is still shown in the machine pools tab wrongly.

 Interestingly if the user opens the machine pools tab of another/different cluster(for ex: ROSA- standalone), the error message still shows wrongly there too.

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. Go back to the cluster list.
7. Open the same cluster again and go to the machine pools tab.
8. See the behavior.
9. Go to back to cluster list and open some other cluster(For ex; ROSA standalone)
10. Go to the machine pools tab and see the behavior.

Actual results:

In step 8, the Machine pool tab still showed the  previously shown error message wrongly in the UI. Reopening the cluster or refresh doesn't clear the error message.
Importantly at step 10, the machine pool tab of totally independent cluster also shown the error message wrongly,

Expected results:

In step 8, the Machine pool tab shouldn't show any error message in the UI.

It should never show an error message related to another cluster in case the user opens the machine pools tab of another/different cluster(for ex: ROSA- standalone) in above circumstance.

Additional info:

Attached screen capture for the same. ErrorMsg.mp4