VMs are failing to Auto Import via VM Discovery
search cancel

VMs are failing to Auto Import via VM Discovery

book

Article ID: 382770

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • VMs are failing to import after moving them to a Cloud Director managed resource pool in vCenter. 

  • cell-management-tool debug-auto-import shows the following error message:
    1) Virtual machine is not present in a vCD managed resource pool.

  • vcloud-container-debug.log located in /opt/vmware/vcloud-director/logs shows the following error message:
    com.vmware.vcloud.api.presentation.service.BadRequestException: Cannot import auto discovered VM from VC because port group null is connected to VC network none, which is not a valid Organization VDC network.

Environment

10.x

Resolution

VMware Cloud Director is not recognizing the portgroups as valid OvDC Networks.


1. Remove the problematic networks from the VM via vCenter. 

2. Delete the OvDC Networks in VMware Cloud Director for this OvDC. 

3. Delete the Portgroups for these OvDC Networks in vCenter. 

4. Re-Create the Portgroups in vCenter and the OvDC Networks in VMware Cloud Director. 

5. Reconnect the VM nics to the correct networks. 

Additional Information

This can occur if the portgroups are migrated from another vCenter Server.