VCF Workload Domain Import Fails with "vCenter Server SDDC Manager extension presence"
search cancel

VCF Workload Domain Import Fails with "vCenter Server SDDC Manager extension presence"

book

Article ID: 427523

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer 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/domainmanager.log 
    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/domainmanager/brownfield/######-####-####-####-#########/output/guardrails_report_############.csv 
    "VcManager","vCenterFQDN","Import","WARNING","VALIDATION_FAILED","vCenter Server SDDC Manager extension presence","Check that the vCenter Server does not have a SDDC Manager extension registered","Found an existing SDDC Manager extension on this vCenter Server. A vCenter should be managed by only one SDDC Manager. Do not import this vCenter into the SDDC Manager if it is already managed by another SDDC Manager and not the current one.","If the vCenter is not managed by other SDDC Managers, then it is safe to import. Note that this can happen if there are previously failed import attempts against the same SDDC Manager.

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

The failure is triggered by a guardrail check as the target vCenter Server contains a stale or existing SDDC Manager extension key (typically com.vmware.sddcManager). This typically occurs in two scenarios:

  1. The vCenter was previously managed by a different VCF instance and was not properly decommissioned.

  2. A prior attempt to import this vCenter into the current SDDC Manager failed after the extension was already registered but before the process completed, leaving a "zombie" registration.

Resolution

To resolve this issue, the stale extension must be manually unregistered from the vCenter Server's Managed Object Browser (MOB) so the new import process can claim ownership.

Note: By default the vCenter MOB is disabled, enable it as per the steps mentioned in the document 401669

  1. Access the vCenter MOB: Open a web browser and navigate to https://<vCenter_FQDN>/mob.

  2. Navigate to Extension Manager:

    • Log in with [email protected] (or equivalent) credentials.

    • Click on content.

    • Click on extensionManager.

  3. Identify the Extension: Locate the extensionList and confirm the presence of the key: com.vmware.sddcManager.

  4. Unregister the Extension:

    • Click on the UnregisterExtension method link at the bottom of the page.

    • In the value field, enter the exact string: com.vmware.sddcManager.

    • Click Invoke Method. A "void" result confirms the command was processed.

  5. Verify Removal: Refresh the extensionManager page to ensure the key is no longer listed in the extensionList.

  6. Retry Import: Return to the SDDC Manager UI and restart the Workload Domain import process.

Note: For further details, refer to Broadcom Knowledge Base Article 344648.

Powered by Wolken Software