"class com.vmware.ssdc.util.LMException" error when perorming a cross vCenter move of VMs to vApps

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Unable to move VMs to vApps backed by Provider VDC in different vCenter Servers.
• Within the Cloud Director UI the following exception is visible "class com.vmware.ssdc.util.LMException".
• Within the Cloud Director UI the VM moves to the new vApp, but in vCenter Server it remains within the original vApp.
• Move VM tasks performed within the same vCenter Server are successful.
• Within the log file /opt/vmware/vcloud-director/logs/vcloud-container-debug.log the following error is visible:

2022-12-06 10:49:14,983 | ERROR  | task-service-activity-pool-19737 | FutureUtil           | Task future is not complete. | requestId=<REQUEST_UUID>,request=POST https://cloud.example.com/api/vApp/vapp-<VAPP_UUID>/action/recomposeVApp,requestTime=1670323739916,remoteAddress=<IP>:28082,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/201...,accept=application/*+xml;version 36.3 vcd=<VCD_UUID>,task=<TASK_UUID> activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:<TASK_UUID>)
com.vmware.ssdc.util.LMException:
    at com.vmware.ssdc.util.LMException.wrap(LMException.java:128)
    at com.vmware.ssdc.library.ExceptionFactory.createFromMultiple(ExceptionFactory.java:32)
    at com.vmware.vcloud.vdc.impl.ComposeRecomposeVAppActivity$FinalizeRecomposePhase.invoke(ComposeRecomposeVAppActivity.java:1333)
    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.vdc.impl.LinkVMsToTargetVAppActivity$LinkVMsToVAppException:
    at com.vmware.vcloud.vdc.impl.LinkVMsToTargetVAppActivity$DelinkVAppVMsToTargetVAppPhase.invoke(LinkVMsToTargetVAppActivity.java:535)

Environment

VMware Cloud Director 10.x

Cause

This issue occurs because Cloud Director is unable to successfully update the storage policy of the VM to the new storage policy on the destination OrgVDC when a cross vCenter move operation is also performed.

Resolution

This issue is resolved in Cloud Director 10.4.1 available at VMware Downloads.

Workaround:

To workaround the issue the following activity can be performed:

1. Create a storage profile with the same name on both the source and destination Provider VDC's and OrgVDC's. 
2. Attach the VM to the above storage profile on the source OrgVDC.
3. When moving the VM, select the storage profile with the same name on the destination vApp.