vApp Power-On Fails in VCD: Distributed Virtual Port Group Name Already Exists

Products

• VMware Cloud Director

Issue/Introduction

vApp power-on operations fail in VMware Cloud Director (VCD). During the deployment sequence, the following error messages are observed in the vCenter Server tasks or VCD UI:

Failed to create distributed virtual port group "dvs.XXXXXXX" because a distributed virtual port group of that name already exists. The DistributedVirtualPort resource "XXXX" is in use. vCenter Server task (moref: XXXX) failed in vCenter Server 'XXXXX' (XXXXX).

Environment

10.3.3.1

Cause

A duplicate distributed virtual port group exists in the backing vCenter Server inventory with an active Virtual Machine connected to it. This stale object prevents VCD from successfully recreating the required network during the vApp power-on sequence due to an identifier and port binding conflict.

Resolution

1. Log in to the backing vCenter Server using the vSphere Client.
2. Confirm that a portgroup already exists with the name in vcd error log
3. Rename the portgroup appending for example OLD into the end of the name
4. Try the power on now from vCloud which should now work
5. Confirm that a new portgroup was now created and the powered on VM is connected to it
6. Confirm if any VM is using the old portgroup and if so, move them to the newly created
7. Delete the stale distributed virtual port group from the vCenter Server inventory to fully resolve the inconsistency.