Unable to create a VM using OVA template from content library

Products

• VMware vCenter Server

Issue/Introduction

• Creating a VM using ova template from content library is getting stuck at 0%
• ESXi host from different cluster is automatically selected instead of ESXi hosts from the selected cluster
• Errors are seen in /var/log/vmware/content-library/cls.log, we also see the source ESXi host is host01 which does not belong to the cluster customer selected 

• Error during transfer of ds:///vmfs/volumes/##############//testova/testova.vmdk: Operation timed out.
  com.vmware.vim.binding.vim.fault.Timedout: Operation timed out.
  OVF import session ########-####-####-####-############ failed with server error.
  com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
      messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
      id = com.vmware.ovfs.ovfs-main.ovfs.transfer_failed,
      defaultMessage = Transfer failed: Error during transfer of ds:///vmfs/volumes/##############//testova/testova.vmdk: Operation timed out..,
      args = [Error during transfer of ds:///vmfs/volumes/##############//testova/testova.vmdk: Operation timed out.],
      params = <null>,
      localized = <null>
  }],
      data = <null>,
      errorType = SERVICE_UNAVAILABLE
   ImportSession ########-####-####-####-############ timeout is 10 minutes
  
  
  Selecting hosts using connectivity: HostConnectivity: Source DS: datastore-###3, Destination DS: datastore-####4
  ...Common hosts: []
  ...Source hosts: [host-##1]
  ...Destination hosts: [host-##2, host-#3, host-##4, host-##5, host-##6,]
  Hosts connected to datastore 'datastore-###3'
  host-##1        host01
  
  Hosts connected to datastore 'datastore-####4':
  host-##2        host02.
  host-##3        host03.
  host-##4        host04.
  host-##5        host05
  host-##6        host06

• Content is not sharable across datacenters

Environment

vSphere vCenter Server 8.0.X

vSphere vCenter Server 7.0.X

Cause

• This is expected behavior as content library datastore is pointing to the datacenter01 instead of pointing to a datacenter02

Resolution

1. Create a content library based on the datastore from the correct datacenter. More at Create a Content Library