SDDC upgrade to 5.2 triggers alarm "Verify Standalone Host Topology"

Products

• VMware SDDC Manager
• VMware Cloud Foundation

Issue/Introduction

• Upgrading to VMware Cloud Foundation (VCF) 5.2.x can trigger a pre-check failure or alarm when the environment includes specific host types such as vSAN witness nodes or HCX ESXi hosts 
• We can see the reference in /var/log/vmware/vcf/operationsmanager/operationsmanager.log

  • grep -i "Entity resource state validation with resource state definition id standalone-host for" operationsmanager.log

    
    

    <date and time> DEBUG [vcf_om,################,2c80] [c.v.e.s.c.v.util.ResponseUtil,pool-3-thread-7] Build validation response: {"errorCode":"BASELINER_ENTITY_RESOURCE_STATE_VALIDATION.info","arguments":["standalone-host","<witness_Node_FQDN>","standAloneHost"],"context":{"severity":"INFO","validation.taskId":"<Unique_identiffier>"},"message":"Entity resource state validation with resource state definition id standalone-host for entity <witness_Node_FQDN> of type standAloneHost succeeded"}

Environment

VMware SDDC Manager 5.2.x

Cause

• This guardrail pre-check has been added to 5.2.x.
• The standalone-host check in vCenter, is failing at it's detecting vsan-witness host as standalone host.
• The process also detects standalone ESXi hosts that are in the environment for HCX functionality.


Resolution

VMware by Broadcom Engineering has acknowledged the error, and are working on remediating this false positive error.

• The Standalone Host pre-check error can be ignored, as it's not going to block vCenter upgrade.
• The precheck should not be ignored when "ingesting" a new VCenter in SDDC.