Add host to cluster validation check failed: Verify topology

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

• Attempting to add a host to a cluster using SDDC Manager fails with the following error:

Message: ADD_HOST operation validation failed due to: ADD_HOST operation validation failed due to: Entity: <HOSTNAME> with failed check: Verify <CLUSTER_NAME> topology with severity CRITICAL

Remediation Message:

Reference Token: ######

• In the /var/log/vmware/vcf/domainmanager/domainmanager.log file, you see the following entry:

YYYY-MM-DDTHH:mm:ss.380+0000 DEBUG [vcf_dm,################################,####] [c.v.v.a.s.AssessmentLambdaServiceClient,dm-exec-8]  Filtered check results are [class LambdaCheckResultRest {
    entityName: <HOSTNAME>
    entityType: VcManager
    description: Validate the number of resources matching definition 'Cluster that has vSAN storage and is not stretched' with condition value == 1
    resultMessage: The number of resources matching definition 'Cluster that has vSAN storage and is not stretched' is incorrect. Count 0, condition value == 1
    severity: CRITICAL
    status: VALIDATION_FAILED
    remediation: null
    name: Verify <CLUSTER_NAME> topology
}]

• The target cluster is not a stretched cluster.
• Unable to add a host in SDDC Manager -The process fails with the error: "Inventory version synchronization failed."

• Reviewing the Operations Manager logs at /var/log/vmware/vcf/operationsmanager/operationsmanager.log -you may see below:

  DEBUG [ [c.v.e.s.c.c.v.vsphere.VcManagerBase,pool-3-thread-9] Connecting to https://ESXI_Hostname:443/sdk Failed to connect to https://############:443/sdk

Environment

VMware Cloud Foundation 5.2

Cause

The 'Cluster Host Data Check' checks for discrepancies between the hosts present in the cluster in vCenter and in the SDDC Manager inventory. A mismatch between the two causes a validation failure, blocking the operation from proceeding.

Resolution

Follow one of the two workarounds below:

Option 1:

Remove the hosts with the error state using the SDDC UI to synchronize the SDDC and vCenter inventories.

Option 2:

Disable the guardrails:

1. Update the file /etc/vmware/vcf/domainmanager/application-prod.properties with following value:
   
   vcf.skip.dayn.guardrails=true 
2. Restart the domainmanager service:
   
   systemctl restart domainmanager
   
   
3. Retry the workflow.

Note: It is recommended to re-enable this flag once the workflow is successful. 

Additional Information

Updating the application-prod.properties file to skip the guardrail is a last resort and should only be done if none of the steps before have resolved the issue.