Error: vCenter upgrade failed. Getting VM group name of stretched cluster failed during initialization in SDDC Manager

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

Upgrading vCenter Server through SDDC Manager fails during the PRE VALIDATION stage. This issue occurs even when the environment does not utilize stretched clusters. The SDDC Manager pre-validation logic attempts to correlate the vCenter Server entity defined in the SDDC database with the human-readable virtual machine label in the vCenter inventory.

• The upgrade process aborts with the error: vCenter upgrade failed. Getting VM group name of stretched cluster failed with exception during initialization.

• The lcm-debug.log contains:
  
  ERROR [vcf_lcm] Upgrade error occured: Getting VM group name of stretched cluster failed with exception during initialization.
Caused by: java.lang.RuntimeException: VM not found
  
  
• vCenter upgrade failed with error "Getting VM group name of stretched cluster failed with exception during initialization"
• In lcm-debug.log:
  YY-MM-DDThh:mm:ss.152+0000 INFO  [vcf_lcm,##################################,9eb5] [c.v.e.s.l.s.impl.UpgradeServiceImpl,http-nio-127.0.0.1-7400-exec-5] Getting list of cluster IDs if the upgrade #######-####-####-####-########### is cluster level upgrade.
YY-MM-DDThh:mm:ss.152+0000 DEBUG [vcf_lcm,##################################,9eb5] [c.v.e.s.l.s.impl.UpgradeServiceImpl,http-nio-127.0.0.1-7400-exec-5] Start collecting the cluster ids for all Cluster level Upgrades
YY-MM-DDThh:mm:ss.152+0000 ERROR [vcf_lcm,################################,9eb5] [c.v.evo.sddc.lcm.model.task.SubTask,http-nio-127.0.0.1-7400-exec-5] Upgrade error occured: Getting VM group name of stretched cluster failed with exception during initialization.
Reference token #####
• The vCenters manage by SDDC is not configure for stretched cluster.

Environment

• VCF 5.x
• VCF 9.x

Cause

The virtual machine inventory label of the vCenter Server in vSphere differs from the entry stored in the SDDC Manager database. This discrepancy can be caused by:Case-sensitivity: A mismatch in letter case (e.g., VCENTER01 vs vcenter01). and Naming Convention: A mismatch between the Fully Qualified Domain Name (FQDN) and the shortname (e.g., vc01.example.com vs vc01).The upgrade pre-validation logic requires an exact match against the inventory label rather than referencing the persistent vCenter object ID.

Resolution

1. Make sure vCenter VM name matches to vCenter shortname. Even after that if the issue still persist, please contact Broadcom Support
   1. Fully Qualified Domain Name (FQDN) = vc01.example.com
   2. short name  = vc01