Description of problem:

1. Add a worker node to a deployed ClusterInstance (scale out scenario) with bad data in the nodeNetworking. In my case the interface name in the default route did not match any interface in the NMState Config.
2. The ClusterInstance renders the BMH and NMStateConfig and inspection begins
3. Inspection fails, the InfraEnv does not create the ISO with a message indicating that the NMStateConfig is invalid (which it is)
4. Edit the ClusterInstance to fix the nmstate configuration of the new node. The webhook blocks the edit.
5. Edit the ClusterInstance to remove the bad node. This succeds, however the bad BMH and NMStateConfig remain on the hub (they aren't deleted)
6. Manually remove the BMH and NMStateConfig from the hubb
7. Edit the ClusterInstance and re-add the node with correct NMState data. BMH and NMStateConfig are re-rendered and scale-out proceeds as expected

Version-Release number of selected component (if applicable):

ACM 2.13.3

How reproducible:

100%

Steps to Reproduce:

1. See above
2.  
3. ...

Actual results:

Expected results:

Ability to edit the clusterinstance to fix the error

Alternatively, I should not need to remove the BMH and NMStateConfig by hand after removing the nodes.

Additional info: