The operation could not be performed because the argument is invalid. A specified parameter was not correct: relocateSpec.profile"/opt/vmware/vcloud-director/logs/vcloud-container-debug.log you see entries similar to:2026-03-20 13:05:23,214 | DEBUG | storage-fabric-activity-pool-1005 | VC20VirtualServer | The target resource pool [vcId=########-####-####-####-############, moref=resgroup-###386] differs from source resource pool [vcId=########-####-####-####-############, moref=resgroup-###428], relocation is necessary | requestId=########-####-####-####-############,request=POST https://vcloud.example.com/api/vApp/vm-########-####-####-####-############/action/reconfigureVm,requestTime=1774011916166,remoteAddress=##.###.###.###:58280,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 40.0.0-alpha vcd=########-####-####-####-############,task=########-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############) activity=(com.vmware.ssdc.backend.services.impl.RelocateVmActivity,urn:uuid:########-####-####-####-############) activity=(com.vmware.vcloud.fabric.storage.storedVm.impl.RelocateStoredVmByStorageClassActivity,urn:uuid:########-####-####-####-############) activity=(com.vmware.vcloud.fabric.storage.storedVm.impl.RelocateStoredVmByDatastoreActivity,urn:uuid:########-####-####-####-############)::2026-03-20 13:05:27,902 | ERROR | task-service-activity-pool-3060 | FutureUtil | Failed to relocate VM to a Hub | requestId=########-####-####-####-############,request=POST https://vcloud.example.com/api/vApp/vm-########-####-####-####-############/action/reconfigureVm,requestTime=1774011916166,remoteAddress=##.###.###.###:58280,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 40.0.0-alpha vcd=########-####-####-####-############,task=########-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############)com.vmware.ssdc.util.RelocateException: Unable to relocate VM. at com.vmware.vcloud.val.internal.impl.RelocateVmActivity$WaitForInventoryUpdatePhase.invoke(RelocateVmActivity.java:397) at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175) at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)Caused by: com.vmware.vcloud.val.exceptions.TaskManagerException: Task failed, vc-id={########-####-####-####-############}, task-moref={ManagedObjectReference: type = Task, value = task-#######, serverGuid = null}, error={A specified parameter was not correct: relocateSpec.profile} at com.vmware.vcloud.val.taskmanagement.AsynchronousTaskWaitActivity$InitialPhase.invoke(AsynchronousTaskWaitActivity.java:149) ... 7 moreCaused by: com.vmware.ssdc.library.exceptions.VimInvalidArgumentException: The operation could not be performed because the argument is invalid. A specified parameter was not correct: relocateSpec.profile at com.vmware.ssdc.library.vim.LmVim.Convert(LmVim.java:262) at com.vmware.ssdc.library.vim.LmVim.Convert(LmVim.java:502) at com.vmware.vcloud.val.taskmanagement.AsynchronousTaskWaitActivity.getResultIfTaskAlreadyCompleted(AsynchronousTaskWaitActivity.java:531) at com.vmware.vcloud.val.taskmanagement.AsynchronousTaskWaitActivity$InitialPhase.invoke(AsynchronousTaskWaitActivity.java:143)Note: VCD can balance the tasks associated with an action across the cells and as such the logs might be spread across different cells in the VCD instance.
VMware Cloud Director 10.6.X
VMware Cloud Director 10.5.X
This issue can occur if the vApp was migrated between OrgVDC's and the migration failed to Move the VM to the correct resource pool.
Verify that the VM is in the correct vCenter resource pool. To do this, compare the Data Center name in the Cloud Director UI with the VM's resource pool name in vCenter. If they do not match, move the VM in vCenter to the appropriate OrgVDC resource pool.