Error: "Specified vApp-scoped VM ID ########-####-####-####-############ does not belong to a VM in the vApp" when moving powered ON vApps between Organization VDCs

Products

• VMware Cloud Director

Issue/Introduction

• Powered ON vApp/VMs are being moved using NSXV2T migrator tool for VMware Cloud Director(VCD).
• Moving the vApp to another OVDC fails with the following error:
  Specified vApp-scoped VM ID ########-####-####-####-############ does not belong to a VM in the vApp.
• vApp has a routed vApp network with NAT configured.
• The ID referenced in the error corresponds to the ID seen in the UI for the NAT rule for the vApp network.
• Not all vApp/VMs with similar configuration are affected

Environment

VMware Cloud Director 10.5

Cause

The issue happens when the NAT rule on the vApp network has an incorrect format. The expected format is <VM Name> and NIC but on the affected VMs, the format is <UUID of the NAT rule> and the NIC.

Resolution

To workaround/resolve the issue, there are 2 options: 

1. 1. Delete the NAT rule form the vApp network services, re-add it and migrate the vApp. For steps to view and add, refer documentation.
   2. Power off the vApp and retry migration.