The Destination Folder is not retained when the VM that is been migrated already exists within this Folder during a RAV migration using HCX within the same VC (Single vCenter Operation)

Products

• VMware HCX

Issue/Introduction

• Migrating a virtual machine using HCX RAV Migration within the same vCenter (Single vCenter Operation) and have selected the "Destination Folder" and the VM already resides in this Folder 
  Note: This issue is only affecting Single vCenter Operation, where the source and target VM are on the same vCenter, but it was migrated to a different cluster (both HCX Manager (source/destination) are also registered to the same vCenter). 
• Post-migration, you observed that the VM is contained in a Folder based off it VM name and not located in the folder it was originally contained in .
• From HCX logs /common/logs/admin/app.log, the following error is observer
  <timestamp>VmotionService_SvcThread-7438, Ent: HybridityAdmin, , TxId: TxId: f92b33d9-####-####-####-############] ERROR c.v.h.s.v.j.PostProcessTargetWorkflow- [migId=74d82c7e-####-####-####-############] Failed to move the VM vm-#### to specified folder with taskId task-#### com.vmware.vim.binding.vim.fault.DuplicateName: The name 'Example_VM' already exists

Cause

Moving the VM to the same folder where the source VM was residing leads to name conflicts within vCenter 

Resolution

This is a condition that may occur in a VMware HCX  environment.

Workaround: 

When selecting the "Destination Folder" ensure that it different to where Folder that this VM is presently located in vCenter