Workload Domain Import Fails with "Import operation for import with id ######-###-###-###-############ failed internally" in VCF 9.x

Products

• VMware SDDC Manager
• VMware Cloud Foundation

Issue/Introduction

• When attempting to import a brownfield Workload Domain into VCF (specifically VCF Operations/SDDC Manager 9.x), the process fails at "Import provided Infrastructure into SDDC Manager as a workload domain" stage.
• Error message on the SDDC manager UI

  Description: 
  Import provided infrastructure into SDDC Manager as a workload domain
  
  Progress Messages: 
  Import operation for import with id ########-####-####-######### failed internally.
  Command was python3 /opt/vmware/vcf/domainmanager/scripts/vcf-import-tool/vcf_brownfleld.py import -- skip-ssh-thumbprint-validation -- sso-user.
  [email protected] -- domain-name <domain name> -- vcenter <vCenter name> -- internal-vcf-auth -- nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json -- skip-nsx-overlay -- output-dir /var/log/vmware/vcf/domainmanager/brownfleld/########-####-####-#########/ --non-interactive. Please check the log files located in /var/log/vmware/vcf/domainmanager/brownfield/########-####-####-#########/ on the SDDC Manager appliance
  
  Error: 
  Message: Import operation for import with id ########-####-####-######### 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 <domain name> -- vcenter <vCenter name> -- internal-vcf-auth --nsx-deployment-spec-path/tmp/nsxDeploymentSpec.json -- skip-nsx-overlay --output-dir /var/log/vmware/vcf/domainmanager/brownfield/########-####-####-#########/ -- non-interactive. Please check the log files located
  In /var/log/vmware/vcf/domainmanager/brownfield/########-####-####-#########/ on the SDDC Manager appliance
  Remediation Message:
  Reference Token: #####
  

  
  
• Domain manager logs shows following error /var/log/vmware/vcf/domainmanager

   ERROR [vcf_dm,#############] [c.v.e.s.o.model.error.ErrorFactory,dm-###-22]  [####] IMPORT_OPERATION_FAILED Import operation for import with id ######-###-###-###-######## 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 <Domainame> --vcenter <vCenter FQDN> --internal-vcf-auth --nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json --skip-nsx-overlay --output-dir /var/log/vmware/vcf/domainmanager/brownfield/######-###-###-###-########/ --non-interactive. Please check the log files located in /var/log/vmware/vcf/domainmanager/brownfield/######-###-###-###-########/ on the SDDC Manager appliance
   

• Error in /var/log/vmware/vcf/domainmanager/brownfield/######-###-###-###-############ /vcf_brownfield.log

  [ERROR] request_helper:31: Result status code from ESC[91minventory import: 500ESC[00m
  [CRITICAL] import_domain:200: Could not import the information for the new domain in SDDC Manager: Could not import inventory into SDDC Manager. Please review '/var/log/vmware/vcf/commonsvcs/vcf-commonsvcs.log' for further details.

• Error in /var/log/vmware/vcf/commonsvcs/vcf-commonsvcs.log

  ERROR [common,######-###-###-###-############ ,39##] [c.v.e.s.i.s.EsxiInventoryServiceImpl,http-nio-##########-###-92] ESXi <hostaname>already exist: ######-###-###-###-############  <hostname> already exists
  ERROR [common,######-###-###-###-############ ,39##] [c.v.e.s.i.s.e.DomainExtensionsImpl,http-nio-##########-###-92] Failed to post domain inventory com.vmware.evo.sddc.inventory.model.InventoryAlreadyExistsException: ######-###-###-###-############  <hostname> already exists

 

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

The failure is caused by a Database Mismatch. The ESXi hosts intended for the new workload domain are already present in the SDDC Manager’s database , likely left over from a previous failed deployment or a decommission process that did not clean up the database entirely.

When the import script attempts to register these "new" hosts, the commonsvcs layer rejects the entry because the Hostname or UUID is already indexed in the SDDC Database

Resolution

To resolve this, the stale entries of the host must be manually removed from the SDDC Manager database before retrying the import. This issue requires assistance from Broadcom Technical Support. We recommend contacting Broadcom Support for further investigation.