Error: "Virtual machine is too recent to be considered for import" causing Virtual Machine not to get auto imported with VM Discovery

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:<VM name>, moref vm-#### in VC <vCenter name> 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 too recent to be considered for import. Its change_version field should be older than timespan defined by VM_DISCOVERY_MIN_AGE_SEC (current value 3600 seconds) or it should have a record of task in task_inv whose status is 3 (COMPLETED).
  
  
• VM discovery is already enabled in VMware Cloud Director (VCD).
• The virtual machine (VM) is present in an appropriate resource pool for the organization.
• Virtual Machine is recently reconfigured.

Environment

VMware Cloud Director 10.6.1.2

Cause

By default, the minimal VM age is configured to 1 hour. This means VMs that were freshly reconfigured are skipped for the import.

Resolution

VM would be considered for Auto-Import after 3600 seconds or the interval can  be changed with the following CMT command. In this example, the age is set to 60 seconds:

opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n VM_DISCOVERY_MIN_AGE_SEC -v 60

Additional Information

Debugging vCenter VM Discovery in VMware Cloud Director