Error: "Failed to load NSX Cluster from the Inventory" during Brownfield vCenter Import in VCF 9.x
search cancel

Error: "Failed to load NSX Cluster from the Inventory" during Brownfield vCenter Import in VCF 9.x

book

Article ID: 429414

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

During a VMware Cloud Foundation (VCF) brownfield import, the workflow fails at the step "Import provided infrastructure into SDDC Manager as a workload domain" with the following message:

Import operation for import with id <UUID> failed internally. Command was python3 /opt/vmware/vcf/domainmanager/scripts/vcf-import-tool/vcf_brownfield.py import --skip-ssh-thumbprint-validation --sso-user [email protected] --domain-name wld-prod --vcenter <FQDN> --internal-vcf-auth --nsx-fqdn <FQDN> --output-dir /var/log/vmware/vcf/domainmanager/brownfield/<UUID>/ --non-interactive. Please check the log files located in /var/log/vmware/vcf/domainmanager/brownfield/<UUID>/ on the SDDC Manager appliance

This issue occurs under the following conditions:

  • The NSX-T Cluster is shared with another VI workload domain that has already been successfully imported.
  • The FQDN of the NSX-T Manager is configured using mixed-case or upper-case characters.

The following error will be observed in /var/log/vmware/vcf/domainmanager/domainmanager.log:

[YYYY-MM-DD HH:mm:ss,000] [ERROR] import_domain:230: An error occured while marking NSXT Clusters as ACTIVE
Traceback (most recent call last):
  File "/opt/vmware/vcf/domainmanager/scripts/vcf-import-tool/domain_import/import_domain.py", line 228, in import_domain_in_sddc_manager

Environment

VMware Cloud Foundation 9.x

Cause

The import script logic performs a case-sensitive string comparison between the provided FQDN in the import specification and the FQDN registered within the NSX Manager inventory.

If there is a case mismatch (e.g., nsx-t.example.com vs. Nsx-T.example.com), the validation fails to identify the existing NSX cluster.

Resolution

This issue will be resolved in future version of VCF 9.x.

If you encounter this issue, please contact Broadcom Support for assistance.