Description of problem:
While adding a new machine pool from a ROSA hypershift cluster, user has chosen a private subnet ID and created successfully. User has selected another ROSA hypershift cluster to add a new machine pool for the same but the private subnet ID fails to fetch as it reported an error as expected due to inexisting of ARNs but the private subnet ID has set based on previous action in first cluster. i.e  the default value of previous cluster's private subnet set as wrongly and it should be "No data found".

How reproducible:

 Always

Steps to reproduce:

1. Launch OCM UI staging.
2. Open ROSA Hypershift cluster.
3. Go to machine pools tab > click on "Add machine pool"
4. Select the private subnet ID and fill all required fields and create it.
5. Go back to cluster list , Choose another ROSA hypershift cluster ( make sure the ARN of used to install the cluster is no more available).
6.  Go to machine pools tab > click on "Add machine pool"
7. See the value of private subnet id from the dialog.

Actual results:
In step 7, the private subnet id value set as default value of the private subnet id of the first  cluster ( Cluster associated in Step 4). This is wrong.

Expected results:
Set always the private subnet id as  "No data found" in case any error and fails to fetch the private subnet ID from add machine pool. 

Attached screen recordings PrivateSubnetsWrongValue.mp4