Virtual Machines which are modified using the Quick Search feature in Cloud Director are renamed and networking changes applied.

Products

• VMware Cloud Director

Issue/Introduction

• Virtual machines which are located using the Quick Search function and then have hardware modifications made are unexpectedly renamed in vSphere to match another virtual machine in the same vApp.
• The MAC address and IP on the network interface of the renamed virtual machine becomes a duplicate of the second virtual machine in the vApp.
• Within Cloud Director the virtual machine is not renamed. It keeps the original name.
• Within Cloud Director the following error is visible on the virtual machines task history:

"could not update: [com.vmware.vcloud.common.model.VAppVmModel#<VAPPVM_UUID>] ERROR: duplicate key value violates unique constraint "uk_vapp_vm_vapp_id_name" Detail: Key (vapp_id, name)=(<VAPP_UUID>, <VM_NAME>) already exists."

Environment

VMware Cloud Director 10.x

Cause

This issue occurs due to a cache timing issue that can occur when VMs located with the Quick Search feature have modifications made to them. Any modification made to the VM, such as adding a hard disk, may trigger the issue.

Resolution

This issue is resolved in the Cloud Director 10.3.3.4, 10.4.2, and later releases available here.

Workaround:

Before upgrading to a version of Cloud Director where the issue is resolved, avoid modifying virtual machines which have been located using the Quick Search function.

When modifications are being made to a VM then it's recommended to either:

1. Locate the virtual machines using manual navigation in the Cloud Director interface.
2. Modify the virtual machines using the Cloud Director API.

Additional Information

Environments which have a slow network connection to Cloud Director have a higher probability of encountering the issue.