Operational Defect Database
BugZero updated this defect 46 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97455
Horizon admin console is not loading after upgrading to 2312
Last update date:
4/3/2024
Affected products:
Horizon
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
In Horizon Connection Server, you see these errors similar to :2024-03-12T19:53:17.208-07:00 WARN (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Certificate CertificateId:[issuer=CN=xxxxxx.certsso.vdi.vmware.com,serial=59648306213191121459708101582141891896]: wrong subject: 'xxxxxx.certsso.vdi.vmware.com'2024-03-12T19:53:17.271-07:00 INFO (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Removed unusable certificate CertificateId:[issuer=CN=xxxxxx.certsso.vdi.vmware.com,serial=59648306213191121459708101582141891896]2024-03-12T19:53:17.271-07:00 DEBUG (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Imported 1 signing certificates and 0 encryption certificates from LDAP, total=22024-03-12T19:53:17.271-07:00 DEBUG (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Choosing preferred credential2024-03-12T19:53:17.271-07:00 ERROR (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Cannot initialise shared credentials manager: No valid certificates exist2024-03-12T19:53:17.287-07:00 DEBUG (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Cannot initialise shared credentials manager com.vmware.vdi.logger.Logger.debug(Logger.java:44)com.vmware.vdi.sharedcredman.SharedCredException: No valid certificates existcom.vmware.vdi.sharedcredman.SharedCredException: No valid certificates existat com.vmware.vdi.sharedcredman.SharedCredManager.a(SourceFile:732)at com.vmware.vdi.sharedcredman.SharedCredManager.a(SourceFile:732)at com.vmware.vdi.sharedcredman.SharedCredManager.e(SourceFile:377)at com.vmware.vdi.sharedcredman.SharedCredManager.e(SourceFile:377)at com.vmware.vdi.sharedcredman.SharedCredManager.initAndRegister(SourceFile:145)at com.vmware.vdi.sharedcredman.SharedCredManager.initAndRegister(SourceFile:145)2024-03-12T19:53:17.287-07:00 DEBUG (1CF4-25A8) <ws_tomcatservice_init> [SharedCredManager] Deregistering shared credentials manager....2024-02-24T04:45:06.660+08:00 DEBUG (33C0-12B8) <ws_tomcatservice_init> [SharedCredManager] Deregistering shared credentials manager2024-02-24T04:45:06.660+08:00 ERROR (33C0-12B8) <ws_tomcatservice_init> [ServerConfigurationFilter] Broker failed to start up
Cause
When the subject name of default signing certificate (vdm.ec) doesn't contain the clusterGUID, admin UI fails to come up after upgrade to 8.12
Resolution
This issue is addressed in Horizon 8.12.1 or later release, hence Customers have to upgrade to 8.12.1 or later release.
Workaround
No workaround available
