Description of problem:

ACM 2.8 / Submariner 0.15

Environment:

ACM Hub cluster and two managed clusters with submariner deployed.
When I started a deletion of the managed clusters without uninstalling the submariner, I expect the managed clusters to be deleted with submariner resources created.

During the uninstall process, the managed clusters got deleted successfully and submariner gw node has been delete as well.
But on the hub, the managed cluster has switched from "Destroying" to "Detaching" state and got stuck in this state.

The managedcluster CR has the following finalizers appear:

finalizers:
  - managedcluster-import-controller.open-cluster-management.io/cleanup
  - cluster.open-cluster-management.io/submariner-agent-cleanup 

As per acm-qe, the managed cluster stuck in the "Detaching" state because the submarienr finalizer is not being deleted.

Adding acm must-gather logs of acm.