Description of problem:

When importing a cluster that was previously installed using ABI or IPI, the corresponding ClusterInstance incorrectly reports its status as Provisioning in progress, even though the cluster has already been successfully provisioned.

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

How reproducible:

Steps to Reproduce:

1.  Import cluster using UI
2. In ZTP app for clusters make the prune disabled
3.  Create a ClusterInstance yaml file that represents correctly the cluster including Networking, and push to git. ZTP/gitOps should pick it up
4. check CRs from cli
5. for cr in bmh,hfs,clusterdeployment,agentclusterinstall,infraenv,nmstateconfig,configmap,klusterletaddonconfig,secrets,clusterinstance; do echo $cr; oc get $cr -n lzhocp ; done
6. clusterinstance will show 

NAME                                                           PAUSED   PROVISIONSTATUS   PROVISIONDETAILS                    AGE
clusterinstance.siteconfig.open-cluster-management.io/ClusterXYZ            Unknown           Waiting for provisioning to start   4h8m

Actual results:

Expected results:

For imported clusters that are already provisioned, the ClusterInstance status should reflect a completed state rather than indicating ongoing provisioning.

Additional info: