Provisioning restored volume from snapshot failed in another vcenter with the following error:

      Warning  ProvisioningFailed    46s (x9 over 5m7s)     csi.vsphere.vmware.com_vmware-vsphere-csi-driver-controller-765d986675-kqww4_40cf6aa6-7dbe-4493-86d6-f9338498e9cb  failed to provision volume with StorageClass "mystorageclass-zs4slqud": rpc error: code = Internal desc = failed to create volume. Errors encountered: [failed to get the compatible shared datastore for create volume from snapshot "e3aca604-ec41-4aaf-a882-51b35d07fb04+d0ad4f6b-9b56-450d-8a08-fe60b2f6eb5e" in vCenter "vcenter.devqe.ibmc.devcluster.openshift.com"]

The origin pvc is under zone "us-west-1a" in vcenter "vcenternested.devqe.ibmc.devcluster.openshift.com", but the restored pvc is under "us-east-1a" in vcenter "vcenter.devqe.ibmc.devcluster.openshift.com"

    4.19.0-0.nightly-2024-12-21-202735

    More than 50% in my test bed

    1. Create vSphere cluster across the multi vcenters
    2. Create origin pvc (with thin-csi) and pod 
    3. Create volumesnapshot taking from the origin pvc
    4. Create restored pvc (with thin-csi) from volumesnapshot and pod     
    5. Check pod and pvc status

 The pvc provisioning failed with error:
 Warning ProvisioningFailed 46s (x9 over 5m7s) csi.vsphere.vmware.com_vmware-vsphere-csi-driver-controller-765d986675-kqww4_40cf6aa6-7dbe-4493-86d6-f9338498e9cb failed to provision volume with StorageClass "mystorageclass-zs4slqud": rpc error: code = Internal desc = failed to create volume. Errors encountered: [failed to get the compatible shared datastore for create volume from snapshot "e3aca604-ec41-4aaf-a882-51b35d07fb04+d0ad4f6b-9b56-450d-8a08-fe60b2f6eb5e" in vCenter "vcenter.devqe.ibmc.devcluster.openshift.com"]

    The pvc provisioning should succeed and pod should be running.