"Cannot move a vApp that is currently involved with an existing move operation" error when performing NSXV to NSXT migration
Article ID: 325497
Updated On:
Products
Issue/Introduction
- Performing NSXV to NSXT migration using VMware NSX Migration for VMware Cloud Director.
- During migration the following error is seen
2023-10-09 15:47:43,733 [threadUtils]:[_runThread]:78 [ERROR] [<ORG_VDC_NAME>] | Error: Failed to move vApp - <VAPP_NAME> with errors [ <REQUEST_UUID> ] Cannot move a vApp that is currently involved with an existing move operation.
2023-10-09 15:47:43,780 [vcdOperations]:[createMoveVappVmPayload]:1768 [DEBUG] [<ORG_VDC_NAME>] | Getting VM - <VM_NAME> details
2023-10-09 15:47:43,780 [threadUtils]:[_runThread]:79 [DEBUG] [Org_name] | Traceback (most recent call last):
File "src\commonUtils\threadUtils.py", line 66, in _runThread
File "src\core\vcd\vcdValidations.py", line 53, in inner
File "src\core\vcd\vcdOperations.py", line 4990, in moveVappApiCall
Exception: Failed to move vApp - <VAPP_NAME> with errors [ <REQUEST_UUID> ] Cannot move a vApp that is currently involved with an existing move operation.
Environment
Cause
This issue is caused when the vApp migration fails, and the vApp with -generated in its name is not deleted from the target Org VDC.
The migration tool will not be able to migrate nor rollback as long as the vApp with name <VAPP_NAME>-generated is present in the target Org VDC.
Resolution
To resolve the issue please perform the below steps:
- If the generated destination vApp with name like <VAPP_NAME>-generated contains VMs, manually move the VMs to the original Organization VDC from Cloud Director. For steps on performing this action reference the Cloud Director documentation, Move a VM to a different vApp.
- After confirming no VMs are present, delete the enerated destination vApp with name like <VAPP_NAME>-generated in the new destination Organization VDC.
- Run the VMware NSX Migration for VMware Cloud Director migration command again to continue the attempt.
Feedback
