"Failed to start vc-ws1a-broker services" Error when attempting to update vCenter Server to 8.0U2

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

UI for failed patching attempt shows "Installation Failed" with reason "Exception occurred in postInstallHook for last_component:Patch"
Checking the /var/log/vmware/applmgmt/PatchRunner.log shows entries similar to the following:

Performing start operation on profile: ALL...
, stderr=Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start vc-ws1a-broker services. Error: Operation timed out

Checking the /var/log/vmware/vc-ws1a-broker/federation-service.log shows entries similar to the following:

2023-10-03T11:07:25,201 WARN vcenter.domain.local:federation (main) [-;-;-;-;-;-] org.springframework.context.annotation.AnnotationConfigApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/vmware/vidm/federation/datastore/RdsDataStoreAutoConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.DatabaseException: java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 8.0.2

Cause

A DNS resolution issue in the JDBC connection to postgres causes a timeout to occur on establishing a connection to the database before the vc-ws1a-broker service can be initialized.

Resolution

The issue is resolved in the release vCenter Server 8.0 Update 2a Build 22617221
Release Notes
Customer Connect Download Link

Workaround:
There is no workaround for this issue.