"There are no active hosts in the cluster" error occurs when performing a cross cluster vMotion

Products

• VMware vCenter Server

Issue/Introduction

 

• Cross cluster vMotion fails with the below error:

"There are no active hosts in the cluster"

• vMotion to all hosts directly in the destination cluster works (but not when the cluster itself is selected as the destination)
• In the /var/log/vmware/vpxd/vpxd.log you see entries similar to the following: 

DD-MM-YY-HH-MM-SS info vpxd[04297] [Originator@6876 sub=vpxLro opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee] [VpxLRO] -- BEGIN task-7125587 -- vm-4743 -- vim.VirtualMachine.relocate -- ########-####-####-####-########4228(########-####-####-####-########55ef)
...
DD-MM-YY-HH-MM-SS error vpxd[04297] [Originator@6876 sub=VmProv opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee-01] Failed to populate VmLocation object. Removing incomplete dstLoc entry.
DD-MM-YY-HH-MM-SS error vpxd[04297] [Originator@6876 sub=VmProv opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee-01] Get exception while executing action vpx.vmprov.SelectDestination: N3Vim5Fault21NoActiveHostInCluster9ExceptionE(Fault cause: vim.fault.NoActiveHostInCluster
...
--> startTime = "DD-MM-YY-HH-MM-SS",
--> dstResult = (vim.host.VMotionManager.VMotionResult) null,
--> srcResult = (vim.host.VMotionManager.SrcVMotionResult) null,
...
DD-MM-YY-HH-MM-SS error vpxd[04297] [Originator@6876 sub=vpxLro opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee-01] [VpxLRO] Unexpected Exception: N3Vim5Fault21NoActiveHostInCluster9ExceptionE(Fault cause: vim.fault.NoActiveHostInCluster
...
DD-MM-YY-HH-MM-SS info vpxd[04297] [Originator@6876 sub=vpxLro opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee] [VpxLRO] -- FINISH task-7125587
DD-MM-YY-HH-MM-SS info vpxd[04297] [Originator@6876 sub=Default opID=xxxxxxxx-353007-auto-7kds-h5:xxxxxxxx-ee] [VpxLRO] -- ERROR task-7125587 -- vm-4743 -- vim.VirtualMachine.relocate: vim.fault.NoActiveHostInCluster:
 

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

• Multiple VM Migration also fails randomly when the source network port groups is not available in the destination cluster.

Environment

VMware vCenter Server 6.7.x
VMware vCenter Server 7.0.x

VMware vCenter Server 8.0.x

Resolution

Broadcom Engineering is working on a fix for this issue. See workaround below.

Workaround:
In the UI migration wizard choose 'Change both compute resource and storage' but maintain the same datastore.