Error "Internal Server Error" when migrating VM replica files using Migrate Tenant Storage

Products

• VMware Cloud Director
• VMware Cloud Director Availability - Migration 4.x

Issue/Introduction

• Using the Migrate Tenant Storage option in the Cloud Director UI to migrate VMs from one vSphere cluster to another cluster which is managed by the same Provider VDC.
• The migration fails with error "Internal Server Error - The operation failed because no suitable resource was found".
• In the Cloud Director log /opt/vmware/vcloud-director/logs/vcloud-container-debug.log messages similar to the following are seen. 

2025-10-15 11:37:07,767 | DEBUG    | Backend-activity-pool-215447 | ResourcePoolAffinityFinder     | Candidate resource pools remaining after handling resource pool affinity requirements: [] | requestId=########-####-####-####-#######,request=POST https://cloud.example.com/api/admin/extension/action/migrateTenant,requestTime=1760528225302,remoteAddress=<ipaddress>,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+json;version 40.0.0-alpha vcd=########-####-####-####-#######,task=########-####-####-####-####### activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-#######) activity=(com.vmware.vcloud.activities.org.TenantStorageMigrationActivity,urn:uuid:########-####-####-####-#######)
 
2025-10-15 11:37:07,768 | ERROR    | Backend-activity-pool-215447 | PlacementSolverImpl            | Couldn't find a hub for subject PlacementSubjectData [id=moref://########-####-####-####-#######/VirtualMachine#vm-###, requirements=[[type:DatastoreAffinity, value:null, vmHomeDatastoreRequirement:[type:DatastoreAffinity, value:[moref://########-####-####-####-#######/Datastore#datastore-###], affinityType:WEAK_AFFINITY], diskDatastoreRequirements:{}], [type:ResourcePoolAffinity, value:[moref://########-####-####-####-#######/ResourcePool#resgroup-###], affinityType:STRONG_AFFINITY]

• The VMs in the OrgVDC are replicated using VMware Cloud Director Availability (VCDA)

Environment

VMware Cloud Director 10.6.1

VMware Cloud Director Availability 4.7.3.1

Cause

This issue occurs as the VM replica created by VCDA has a strong affinity to the source cluster.

VM replications created by VCDA should only be migrated by VCDA itself, not by the Migrate Tenant Storage option in the Cloud Director UI.

Resolution

The placement location of VM can be updated by editing the Storage Policy on the VM in VCDA. Select a storage policy which is only available to the target vSphere cluster. This will trigger a RelocateVM task in Cloud Director, which in turn will migrate the VM in vSphere if successful.