Workload Domain Import Fails in VCF 9.0 with "Cluster common datastore check" and vSAN Partition Errors
search cancel

Workload Domain Import Fails in VCF 9.0 with "Cluster common datastore check" and vSAN Partition Errors

book

Article ID: 423358

calendar_today

Updated On:

Products

VCF Operations VMware Cloud Foundation VMware SDDC Manager

Issue/Introduction

  • When attempting to import a brownfield Workload Domain (specifically a 2-node vSAN cluster) into VMware Cloud Foundation (VCF) 9.0, the operation fails during the Import Guardrails phase.
  • The SDDC Manager / VCF Ops UI displays an internal failure message 
    Descriptionﾠ				Import provided infrastructure into SDDC Manager as a workload domain
Progress Messagesﾠ		Import operation for import with id f2ca####-####-####-####-########ed22 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 example-domain-name --vcenter importedvcenter.example.com --internal-vcf-auth --nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json --skip-nsx-overlay --output-dir /var/log/vmware/vcf/domainmanager/brownfield/f2ca####-####-####-####-########ed22/ --non-interactive. Please check the log files located in /var/log/vmware/vcf/domainmanager/brownfield/f2ca####-####-####-####-########ed22/ on the SDDC Manager appliance
Error Message: 			Import operation for import with id f2ca####-####-####-####-########ed22 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 example-domain-name --vcenter importedvcenter.example.com --internal-vcf-auth --nsx-deployment-spec-path /tmp/nsxDeploymentSpec.json --skip-nsx-overlay --output-dir /var/log/vmware/vcf/domainmanager/brownfield/f2ca####-####-####-####-########ed22/ --non-interactive. Please check the log files located in /var/log/vmware/vcf/domainmanager/brownfield/f2ca####-####-####-####-########ed22/ on the SDDC Manager appliance
Remediation Message:
Reference Token: Q####I
Cause:

     

  • Error in /var/log/vmware/vcf/domainmanager/domainmanager.log in SDDC Manager shows a 400 error during the guardrails step. 
    DEBUG [vcf_dm,69#########################9e,c770] [c.v.v.v.s.b.u.BrownfieldImportProgressReportService,dm-exec-12]  Deserialized progress report of the task with id f2ca####-####-####-####-########ed22: {"process_id":"f2ca####-####-####-####-########ed22","status":"completed with error","progress":{"step":"1","step_dription":"Run import guardrails to ensure compliance and security."},"total_steps":4,"errors":[{"error_code":"*****","message":"Result status code from set datasource: 400","severity":"ERROR"}]}

     

  • Check Guardrail Reports: Navigate to the brownfield log directory for the specific execution ID: /var/log/vmware/vcf/domainmanager/brownfield/[UUID]/output/. Review guardrails_report_[vcenter].yml or .csv 
    "cluster","imported-cluster-vcf-test","ESX Upgrade","ERROR","VALIDATION_FAILED","Cluster common datastore check.","Validates whether the common datastore for all hosts is VSAN skyline health check compatible or with NFS3 version or FC storage.","No common datastore (vSAN, NFS, or FC) matches import criteria. VSAN storage cannot be used as primary datastore for cluster imported-cluster-vcf-test because of failure in [vsanClusterPartitionTestStatus, vsanObjectHealthStatus]","Please check if the cluster has common datastore for all hosts."

     

  • Error in /var/log/vmware/vcf/operationsmanager/operationsmanager.log in SDDC Manager 
    INFO  [c.v.v.b.c.v.ClusterPrimaryDataStorePreImportValidator,precheck-validation2] Following VSAN datastores java.util.stream.ReferencePipeline$3@2215dcfe has failed VSAN health checks [vsanClusterPartitionTestStatus, vsanObjectHealthStatus]
DEBUG [c.v.v.b.c.v.ClusterPrimaryDataStorePreImportValidator,precheck-validation2] For external storage datastore type, cluster imported-cluster-vcf-test size is supported is: true
ERROR [c.v.v.b.c.v.ClusterPrimaryDataStorePreImportValidator,precheck-validation2] Unable to find healthy datastore entities shared by all hosts in the cluster imported-cluster-vcf-test

The specific validation failure relates to the shared datastores not meeting the import criteria due to vSAN health issues.

Environment

  • VMware Cloud Foundation
  • VMware Cloud Foundation Ops

Cause

  • The import fails because the vSAN cluster is currently in a partitioned state. The pre-import validation (Guardrails) requires the vSAN cluster to be healthy.
  • In this specific scenario, the issue stems from a misconfiguration of the VMkernel adapters on the vSAN Witness Host. The Management VMkernel adapter (typically vmk0 or the designated management interface) had the wrong service enabled for vSAN traffic handling. Specifically, the standard vSAN service was not enabled, or a conflicting/incorrect "vSAN witness" service tag was applied incorrectly in place of the required vSAN traffic service.

Resolution

To resolve this issue, correct the VMkernel network configuration on the vSAN Witness host.

Steps to follow:

  1. Log in to the vCenter Server UI.
  2. Navigate to the vSAN Witness Host.
  3. Go to Configure > Networking > VMkernel adapters.
  4. Select the Management VMkernel adapter.
  5. Click Edit.
  6. Under Available services:
    1. Uncheck "vSAN Witness" (if explicitly present and incorrect for your specific witness appliance configuration logic).
    2. Check the vSAN service.
  7. Click OK.
  8. Retry the Workload Domain import in SDDC Manager.
Powered by Wolken Software