Brownfield import validation to VCF 9.0 fails with error "Detected an existing SDDC Manager extension on this vCenter Server"
search cancel

Brownfield import validation to VCF 9.0 fails with error "Detected an existing SDDC Manager extension on this vCenter Server"

book

Article ID: 404182

calendar_today

Updated On:

Products

VMware vCenter Server VMware SDDC Manager / VCF Installer VMware Cloud Foundation

Issue/Introduction

  • You have installed a new vCenter 9.0. OR upgraded the vCenter to 9.0.
  • When you are performing a Brownfield import of the vCenter to VCF 9.0, you may encounter these errors if there was a previous instance of failed Brownfield import.
    VcManager vcenter.example.com: Detected an existing SDDC Manager extension on this vCenter Server
Remediation: Please ensure that no SDDC Manager extension is registered to the vCenter Server to be imported

VcManager vcenter.example.com : Detected an NSX Manager connected to the vCenter Server
Remediation: Please ensure that no NSX Manager is connected to the vCenter Server to be imported/converted


 

  • 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  administrator@vsphere.local --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","vcenter.example.com","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 Guardrail feature introduced in VCF 9.0 fails if the SDDC Manager extension is already registered to vCenter. In this instance, a previous failed brownfield import left behind stale SDDC and NSX plugins, triggering the Guardrail block.

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. Take a snapshot of the vCenter Server and SDDC Manager. 
  2. Unregister the stale plugins of SDDC and NSX from the vCenter MOB page. Follow KB 344648 to unregister the plugin.
  3. Plugins to unregister:
    • ["com.vmware.sddcManager"]
    • ["com.vmware.nsx.management.nsxt"]
    • ["com.vmware.nsx.management.nsxt.vcp"]
    • ["com.vmware.nsx.management.nsxt.vpc"]
    • ["com.vmware.nsx.management.nsxt.networking"]

     4. Once the plugins are unregistered, re-run the validations in the VCF installer.

Additional Information

  • Extension list from the vCenter 9.0 when a failed Brownfield import is noticed

extensionList["com.vmware.vim.sps.task"]
extensionList["com.vmware.vim.sms"]
extensionList["com.vmware.vim.vsm"
extensionList["VirtualCenter"]
extensionList["com.vmware.vim.stats.report"]
extensionList["com.vmware.vim.vcha"]
extensionList["com.vmware.vcenter.topology.task"]
extensionList["com.vmware.vim.ls"]
extensionList["hostdiag"]
extensionList["com.vmware.vim.sps"]
extensionList["com.vmware.hvc.task"]
extensionList["com.vmware.nsx.management.nsxt.vpc"]
extensionList["com.vmware.vrops.ui"]
extensionList["com.vmware.nsx.management.nsxt"]
extensionList["com.vmware.vcenter.iso"
extensionList["com.vmware.registry"]
extensionList["com.vmware.cl"]
extensionList["com.vmware.vim.eam"
extensionList["com.vmware.ovf"
extensionList["com.vmware.vcenter.vmtx"]
extensionList["com.vmware.vmcam"]
extensionList["com.vmware.sddcManager"
extensionList["com.vmware.vsan.client"]
extensionList["com.vmware.phm"]
extensionList["com.vmware.nsx.management.nsxt.networking"]
extensionList["com.vmware.vsphere.client"]
extensionList["com.vmware.vsphere.update.manager.client"
extensionList["com.vmware.rbd"]
extensionList["com.vmware.vcenter.wcp"]
extensionList["com.vmware.Icm.client"]
extensionlist["com.vmware.vsan.health"]
extensionList["com.vmware.nsx.management.nsxt.vcp"]
extensionList["com.vmware.vcf.client"]
extensionList["com.vmware.vcIntegrity"]
extensionList["com.vmware.vlcm.client"]

  • If you see extension details, it will show the plugin is for version 9.0

Powered by Wolken Software