Error: "Import operation for import with id failed internally" during brownfield import of vCenter Server in VCF 9.x
search cancel

Error: "Import operation for import with id failed internally" during brownfield import of vCenter Server in VCF 9.x

book

Article ID: 409568

calendar_today

Updated On:

Products

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

Issue/Introduction

  • Brownfield import of vCenter Server 8.x into VCF Operations 9.x fails with the 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_Server_FQDN> --internal-vcf-auth -- nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json --output-dir /var/log/vmware/vcf/domainmanager/brownfielde/####/ -- non-interactive. Please check the log fileslocated in /var/log/vmware/vcf/domainmanager/brownfielde/####/ on the SDDC Manager appliance.

  • Sync inventory on VCF ops fails with the error message:

    Import operation for sync with id #### failed internally. Command was python3 /opt/vmware/vcf/domainmanager/scripts/vcf-import-tool/vcf_brownfield.py sync -- domain-name <Domain_name> -- skip-ssh-thumbprint-validation -- internal-vcf-auth -- 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.

  • Following error is observed in /var/log/vmware/vcf/domainmanager/domainmanager.log at Run import guardrails to ensure compliance and security:

    YYYY-MM-DDThh:mm:ss DEBUG [vcf_dm,####,####] [c.v.v.v.s.b.u.BrownfieldImportProgressReportService,dm-exec-30]  Deserialized progress report of the task with id ####: {"process_id":"####","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 INFO  [vcf_dm,####,####] [c.v.v.v.s.b.r.BrownfieldRunnerService,dm-exec-33] Failed guardrails CSV: /var/log/vmware/vcf/domainmanager/brownfield/####/output/guardrails_report_<vCenter_Server_FQDN>.csv
    YYYY-MM-DDThh:mm:ss INFO  [vcf_dm,####,####] [c.v.v.v.s.b.r.BrownfieldRunnerService,dm-exec-33] All guardrails CSV: /var/log/vmware/vcf/domainmanager/brownfield/####/output/guardrails_report_<vCenter_Server_FQDN>_all.csv

  • ESXi upgrade policy validation failure is observed in /var/log/vmware/vcf/domainmanager/brownfield/####/output/guardrails_report_<vCenter_Server_FQDN>.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

VMware Cloud Foundation (VCF) 9.1

VCF Operation 9.1

VMware vCenter Server 8.x

Cause

The import guardrail validation fails due to a configuration mismatch between vCenter Server and SDDC Manager:

  • vCenter Server Setting: The option Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode is currently disabled.

  • SDDC Manager Requirement: The default ESXi upgrade policy requires this VM migration option to be enabled.

Resolution

Configure the remediation settings within vCenter Server:

  1. Lifecycle Manager (Global).

    1. Log in to the target vCenter Server.

    2. Navigate to Lifecycle Manager > Settings.

    3. Under Cluster Lifecycle, select Image and click Edit.

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

    5. Enable Retry policy (if not already selected) and configure:

      1. Retry delay: 5 minutes

      2. Number of retries: 3

    6. Save the changes.

  2. Updates tab at cluster level.

    1. Select the target Cluster.

    2. Navigate to Updates > Hosts > Image.

    3. Under Image Compliance, click on ellipsis on the right > Edit remediation settings.

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

    5. Enable Retry policy (if not already selected) and configure:

      1. Retry delay: 5 minutes

      2. Number of retries: 3

    6. Save the changes.

  3. Retry the import or the inventory sync task.

Additional Information