Brownfield import-Fails to import vCenter 8x to VCF 9.x
search cancel

Brownfield import-Fails to import vCenter 8x to VCF 9.x

book

Article ID: 409568

calendar_today

Updated On:

Products

VCF Operations VMware SDDC Manager / VCF Installer VMware vCenter Server 8.0

Issue/Introduction

  • While starting the brownfield import to vCenter server the task fails with below mentioned error 

    "Import operation for import with id e6##229-####-405a-a##d-aO####ea3 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.lab --domain-name <DOMAIN_NAME>-- <FQDN_OF_VCENTER> --internal-vcf-auth -- nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json --output-dir /var/log/vmware/vcf/domainmanager/brownfielde/6##229-####-405a-a##d-aO####ea3/ -- non-interactive. Please check the log fileslocated in /var/log/vmware/vcf/domainmanager/brownfielde/6##229-####-405a-a##d-aO####ea3/ on the SDDC Manager appliance





  • Error in /var/log/vmware/vcf/domainmanager/domainmanager.log shows failure at "Run import guardrails to ensure compliance and security."
    YYYY-MM-DDThh:mm:ss.109+0000 DEBUG [vcf_dm,68a####3890c####5b2a32####3a587,ecdf] [c.v.v.v.s.b.u.BrownfieldImportProgressReportService,dm-exec-30]  Deserialized progress report of the task with id 41####be-####-426b-####-ffc8####6449: {"process_id":"41####be-####-426b-####-ffc8####6449","status":"completed with     error","progress":{"step":"1","step_description":"Run import guardrails to ensure compliance and security."},"total_steps":4,"errors":[{"error_code":"*****","message":"Result status code from set datasource: ###","severity":"ERROR"}]}

YYYY-MM-DDThh:mm:ss.109+0000 INFO  [vcf_dm,68a####3890c####5b2a32####3a587,6577] [c.v.v.v.s.b.r.BrownfieldRunnerService,dm-exec-33] Failed guardrails CSV: /var/log/vmware/vcf/domainmanager/brownfield/41###be-####-426b-####-ffc####36449/output/guardrails_report_<FQDN_OF_VCENTER>.csv

YYYY-MM-DDThh:mm:ss.109+0000 INFO  [vcf_dm,68a####3890c####5b2a32####3a587,6577] [c.v.v.v.s.b.r.BrownfieldRunnerService,dm-exec-33] All guardrails CSV: /var/log/vmware/vcf/domainmanager/brownfield/41###be-####-426b-####-ffc####36449/output/guardrails_report_<FQDN_OF_VCENTER>_all.csv
  • Upon checking /var/log/vmware/vcf/domainmanager/brownfield/41###be-####-426b-####-ffc####36449/output/guardrails_report_<FQDN_OF_VCENTER>.csv
    Object Type: cluster
       Object Name: <NAME_OF_CLUSTER>
       Day-N Operation: ESX Upgrade
       Severity Level: WARNING
       Status: VALIDATION_FAILED
       Check Name: ESXi upgrade policy validation across vCenter and SDDC Manager
       Description: Checks if upgrade policy configured for cluster <NAME_OF_CLUSTER> on vCenter match default SDDC Manager ESXi upgrade policy
       Details: Evacuate Offline VMs upgrade policy configured for cluster <NAME_OF_CLUSTER> on vCenter does not match default SDDC Manager ESXi upgrade     policy. It has value false in vCenter, and default value true in SDDC Manager.
       Remediation: Review and apply the desired upgrade policy options from the "Upgrade Options" page during "ESX Configure Update".



 

Environment

VCF 9.X

Cause

The cluster remediation setting in the source vCenter Server does not match the default ESXi upgrade policy in SDDC Manager.

  • In vCenter: The VM migration option for powered off and suspended VMs is unchecked.

  • In SDDC Manager: The default ESXi upgrade policy requires “Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode” to be enabled.

This mismatch causes the import guardrail validation to fail.

Resolution

To resolve the issue:

There are 2 places that changes need to be made.

The first will be in Lifecycle Manager and the second will be at the Image Compliance.

The Cluster level is selected, Image is selected, then at Image Compliance, select the 3 dots to the right then choose Edit remediation settings

  • First is Lifecycle Manager

    • Log in to vCenter Server where the import is failing.

    • Navigate to Lifecycle Manager.

    • Click Settings.

    • Under Cluster Lifecycle, select Image.

    • Click Edit.

       

  • Enable the option: Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode

  • Also, if not selected, select "Retry policy"; then set "Retry delay" for 5 minutes; then set "Number of retires" 3.

         

  • Second place a change will need to be done is Image Compliance
    • Select the Cluster level
    • Select Updates
    • Under Hosts select Image 
    • Then at Image Compliance, select the 3 dots to the right then choose Edit remediation settings

         

  • Enable the option: Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode

  • Also, if not selected, select "Retry policy"; then set "Retry delay" for 5 minutes; then set "Number of retires" 3.

       

 

After applying these settings, retry the brownfield import.

 

Additional Information

Powered by Wolken Software