Error: "Abnormal tx termination" seen in Cloud Director container logs for VmDiscoveryBackgroundActivity and no VMs can be imported by auto-discovery

Products

• VMware Cloud Director

Issue/Introduction

• Any and all VMs which are placed in VCD-managed resource pools in vCenter are not successfully imported
• In the vcloud-container-debug.log, there are repeated errors in the PrepareImportVmPhase:
  • Transaction rolled back; session has been closed [Conversation: <UUID>, transaction null, transactionDepth: 0] Transaction opened at: <undefined>
  • [Activity Execution] Abnormal tx termination - Handle: urn:uuid:<UUID>, Current Phase: VmDiscoveryBackgroundJob$VmDiscoveryBackgroundActivity$PrepareImportVmPhase
• You may also see the error "Virtual machine is present in a resource pool (resgroup-xxxxx) not managed by vCD" but this is not the cause of the issue
  • For more information about this error, please see KB 380505 

Environment

VMware Cloud Director 10.6.x

Resolution

To resolve this issue, contact Broadcom Support and note this Article ID (410831) in the problem description.

For more information, please see Creating and managing Broadcom support cases.