vCenter 7.x to vCenter 8.x upgrade precheck error - vCenter Rhttpproxy TLS Certificate has no DNS Name in SubjectAltName

Products

• VMware vCenter Server

Issue/Introduction

When performing an upgrade precheck in advance of an upgrade of vCenter from 7.x to 8x, the following precheck error is encountered

 

vCenter Rhttpproxy TLS Certificate has no DNS Name in SubjectAltName

Certificate - vCenter Rhttpproxy TLS Certificate

FQDN - HOSTNAME.example-second-level-domain.example-top-level-domain

SANS-DNS - hostname.example-second-level-domain.example-top-level-domain

Status - RED

One or more Certificates on vCenter have no or incorrect DNS in SubjectAltName

 

Environment

vCenter 7.x

Cause

The vCenter hostname case may have change from uppercase to lowercase prior to the precheck being run.

The vCenter hostname, PNID and DC Name are not in alignment from a character case perspective.

Resolution

Leverage this article to bring the hostname, PNID and DC Name back into alignment from a character case perspective - 

https://knowledge.broadcom.com/external/article/326214/upgrade-to-vcenter-server-80x-fails-with.html

 

The objective is to have the character case identical for hostname, PNID and DC Name.

Example - all should be HOSTNAME.example-second-level-domain.example-top-level-domain, or all should be hostname.example-second-level-domain.example-top-level-domain

Additional Information

Additional input on the case alignment process can be provided by opening a case with by Broadcom Support.