Auto-import of a virtual machine is not being performed in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• A VM is not being auto-imported and, when attempting to diagnose the issue with the cell management tool, the following symptoms are displayed.
  
  VM with name:#########, moref vm-##### in VC ######### can be skipped for the following reasons:
1) Virtual machine is in an organization which has auto discovery of the virtual machines disabled.
2) Virtual machine is present in a resource pool (resgroup-#####) not managed by vCD
  
  
• VM discovery is already enabled in VMware Cloud Director (VCD).
• The virtual machine (VM) is present in an appropriate resource pool for the organization.
• The item is found to exist in a catalog and has a status of inconsistent.
• The VM is powered on and currently being used.

Environment

VMware Cloud Director 10.6.x

Cause

The virtual machine is a catalog item that is already managed by VCD, so it is not considered a valid target for import.

Resolution

The following procedure is recommended:

1. Schedule a maintenance window.
2. Shut down the virtual machine in a clean state in the underlying vCenter instance, which should remediate the inconsistent status within the catalog.
3. Deploy a new vApp from the catalog item within VCD.
4. Power on and use the newly deployed vApp going forward, leaving the original as a vApp template within the catalog.

Once everything is working as preferred, the catalog item could then be managed or removed, as desired.

Additional Information

There is a known issue for the cell management tool that will present an incorrect error regarding the resource pool, as detailed in the following:

Error: "Virtual machine is present in a resource pool (resgroup-xxxxx) not managed by vCD." in Cloud Director debug-auto-import even though the VM is successfully discovered