...
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.
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.
The vc-ws1a-broker service fails to start resulting in a failed patching of vCenter Server to 8.0U2
The issue is resolved in the release vCenter Server 8.0 Update 2a Build 22617221Release NotesCustomer Connect Download Link
There is no workaround for this issue.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.