Error: "The operation failed because no suitable resource was found" When attempting to Migrate Tenant Storage

Products

• VMware Cloud Director

Issue/Introduction

• Attempting to Migrate Tenant Storage to a new Datastore cluster
• In vCenter you will see the following error "File [<VCD-Content-Catalog>] distributedCatalogs was not found"
• In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log you see entries similar to:
  
  2026-03-25 14:07:02,630 | DEBUG    | task-service-activity-pool-540 | TenantMigrationServiceImpl     | Executing MIGRATE_TENANT_STORAGE | requestId=########-####-####-####-############,request=POST https://vcloud.example.com/api/admin/extension/action/migrateTenant,requestTime=1774447622291,remoteAddress=###.###.###.###:18818,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:########-####-####-####-############)
:
:
2026-03-25 14:07:02,649 | DEBUG    | task-service-activity-pool-540 | TaskActivity                   | [Activity Execution] Waiting on ActivitySupervisionRequest: SupervisedCompletion [activity=com.vmware.vcloud.backendbase.management.system.TaskActivity@7b4ba3f3, activityExecutionState=com.vmware.vcloud.activity.impl.FrameworkActivityExecutionStateImpl@2567420d, activityEventEmitter=ActivityEventEmitterTemplate [activityEventListenerSet=[com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase@3d4cb9c4]], beginTimeMillis=1774447622649, canceled=false, complete=false, futures(size)=1, eventTracker(size)=0, nextPhase=class com.vmware.vcloud.backendbase.management.system.TaskActivity$PostExecutePhase, onComplete=com.vmware.vcloud.activity.executors.LocalActivityExecutor$3@6f988d1d, timeoutNotificationSent=false, timeoutMillis=180000, shortCircuit=false] next phase: class com.vmware.vcloud.backendbase.management.system.TaskActivity$PostExecutePhase - Handle: urn:uuid:########-####-####-####-############, Current Phase: TaskActivity$ExecutePhase | requestId=########-####-####-####-############,request=POST https://vcloud.example.com/api/admin/extension/action/migrateTenant,requestTime=1774447622291,remoteAddress=###.###.###.###:18818,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:########-####-####-####-############)
operation failed because no suitable resource was found. Out of 2 candidate hubs:
        1 hubs eliminated because: No valid storage containers found for Media "########-####-####-####-############". All 34 available storage containers were filtered out as being invalid.  Rejected hubs: resgroup-######
        1 hubs eliminated because: No valid storage containers found for Media "########-####-####-####-############". All 38 available storage containers were filtered out as being invalid.  Rejected hubs: resgroup-######
Storage containers were rejected for the following reasons:
        68 storage containers rejected because: They are not in the list of required datastores. The required datastores are [name: <Datastore-Cluster>, moref: datastore-######].  Rejected storage containers: datastore1 (##), datastore1 (##), datastore1 (##)
        1 storage containers rejected because: They do not support the required storage policy: <Storage-Policy>.  Rejected storage containers: <Datastore-Cluster>, partialFailure=false, partialFailureException=null, nullResult=false, result=null, canceled=false] - Handle: urn:uuid:########-####-####-####-############, Current Phase: TaskActivity$ExecutePhase |
  
  
  

Environment

VMware Cloud Director 10.6.X

Cause

This issue occurs due to the destination datastores not being part of the same storage policy for the source datastores.

Resolution

To resolve this issue ensure that at least one destination datastore is in the same storage policy used for the source datastores.

Additional Information

Migrate VMware Cloud Director Tenant Storage