VCF Import fails when Workload Domain vCenter Cluster is located inside a folder
search cancel

VCF Import fails when Workload Domain vCenter Cluster is located inside a folder

book

Article ID: 446163

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

When performing an import to create a Workload Domain (WLD) in VMware Cloud Foundation (VCF) 9.1.0, the process fails during the import phase (after validation) with an error indicating that the vCenter VM or cluster cannot be found.

The Subtask of importing fails with following error:

Description : Discover the existing domain from vCenter
Progress Messages : Failed to discovery domain inventory with vCenter <vCenter Server FQDN>


Following error can be seen in domainmanager.log :

YYYY-MM-DDTHH:MM:SS.SSS+0000 ERROR [vcf_dm,XXXXXXXXXXXXXXXXXXXXXXXXXX,XXXX] [c.v.v.d.u.DomainDiscoveryClusterHelper,dm-exec-XXX]  Failed to process cluster <Cluster name> in vCenter <vCenter Server FQDN>, skipping
java.lang.ClassCastException: Cannot cast jdk.proxy4.$Proxy432 to com.vmware.vim.binding.vim.Datacenter

YYYY-MM-DDTHH:MM:SS.SSS+0000 ERROR [vcf_dm,XXXXXXXXXXXXXXXXXXXXXXXXXX,XXXX] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-XXX] [LSGNMF] DOMAIN_DISCOVERY_FAILED Failed to discovery domain inventory with vCenter <vCenter Server FQDN>.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to discovery domain inventory with vCenter <vCenter Server FQDN>.

Environment

VMware Cloud Foundation 9.1.0

Cause

This issue is caused by a bug in the SDDC Manager automation framework. The current logic fails to correctly traverse or identify clusters that are nested within folders in the vSphere inventory (e.g., Datacenter > Folder > Cluster).

Resolution

Engineering has confirmed this is a known issue.

Workaround

To unblock the import process, temporarily move the cluster out of the folder so it resides directly under the Datacenter object.

Steps:

  1. Move Cluster: In the vSphere Client, move the cluster containing the WLD vCenter VM out of its current folder and place it directly under the Datacenter.
  2. Perform Import: Retry the import process in SDDC Manager. The cluster should now be correctly identified.
  3. Post-Import (Optional): Once the import/converge process is complete, you may move the cluster back to its original folder structure. This topology is supported by VCF once the initial automation task is finished.

 

Additional Information

This issue can also occur when running a 'Sync Inventory' task within the VCF Operations UI.
Powered by Wolken Software