VCF upgrade on VxRail environment fails on prechecks with error: "Cluster should not be stretched"

Products

• VMware SDDC Manager

Issue/Introduction

Symptoms:

 

• Attempt to upgrade VxRail Manager and ESXi Hosts fails during prechecks with the following error:
  
  Description : Check if cluster is not stretched
  Error Description :  Cluster should not be stretched
  High: Do not perform upgrade without addressing this issue.
  Remediation: The current topology that contains stretch cluster(s) is not supported
  
  
  
  
• Operation manager logs contains errors similar to the excerpt below:
  
  /var/log/vmware/vcf/operationsmanager/operationsmanager.log:
  
  2024-10-22T05:11:42.553+0000 DEBUG [vcf_om,6717340e22dee16dfea3f1b07467e96a,921e] [c.v.e.s.c.v.util.ResponseUtil,pool-3-thread-6] Build validation response: {"errorCode":"BASELINER_ENTITY_RESOURCE_STATE_VALIDATION.error",
"arguments":["cluster-vsan-non-stretched","vcf-xxxx-xxxxxx","cluster"],"context":{"severity":"ERROR","validation.taskId":"7f000001-928c-1187-8192-b29b821603d4"},
"message":"Entity resource state validation with resource state definition id cluster-vsan-non-stretched for entity vcf-xxxx-xxxxxx of type cluster failed"}
2024-10-22T05:11:42.563+0000 DEBUG [vcf_om,6717340e22dee16dfea3f1b07467e96a,921e] [c.v.e.s.c.v.util.ResponseUtil,pool-3-thread-6] Build validation response: {"errorCode":"BASELINER_TARGET_STATE_VALIDATION.error",
"arguments":["host-cluster-vcf-xxxx-xxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"],"context":{"severity":"ERROR","validation.taskId":"7f000001-928c-1187-8192-b29b821603d4"},
"message":"Target state validation for target state with id host-cluster-vcf-xxxx-xxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx failed"}
2024-10-22T05:11:42.564+0000 DEBUG [vcf_om,6717340e22dee16dfea3f1b07467e96a,921e] [c.v.e.s.c.v.util.ResponseUtil,pool-3-thread-6] Build validation response: {"errorCode":"BASELINER_TARGET_STATE_VALIDATION.error",
"arguments":[null],"context":{"severity":"ERROR","validation.taskId":"7f000001-928c-1187-8192-b29b821603d4"},"message":"Target state validation for target state with id null failed"}
  
  
• SDDC manager health check and vCenter Skyline Health does not report any issue related to the vSAN stretched cluster.
  
  
• vSAN Cluster Hardware and disks was verified against the VMware Compatibility Guide

Environment

VMware Cloud Foundation 4.x
VMware Cloud Foundation 5.x

Cause

The cluster(s) was stretched directly from the vCenter outside of SDDC manager.
As a result the SDDC has no awareness of any az2 information.

Resolution

To address this issue the cluster needs to be unstretched and stretched again from the SDDC manager: Stretching vSAN Clusters in VMware Cloud Foundation


Note: If you are unable to perform the un-stretch /re-stretch of the vSAN cluster prior to the upgrade contact VCF support for a workaround.
Though in the longer term the inconsistency with the stretched status of the environment between SDDC and vCenter must be addressed.