Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: 6857e6f3d4bf Known affected version(s) that were inferred because the vendor did not provide any: 8.0.1.00100
If your vCenter Single Sign-On domain contains uppercase letters such as [email protected] or [email protected] , installation, patching and upgrades to vCenter 8.0 Update 1 might fail. During installation or upgrade from an earlier version, in the install wizard, you see an error such as Failed to start the Workload Control Plane Service . During patching from 8.x, in the Virtual Appliance Management Interface, you see the error Exception occurred in postInstallHook . Messages in the /var/log/vmware/wcp/wcpsvc.log file shows a failure such as: 2023-04-17T13:04:54.017Z error wcp [gcauth/gc_auth.go:94] Failed to parse VC JWKS: invalid character '<' looking for beginning of value 2023-04-17T13:04:54.017Z error wcp [gcauth/gc_auth.go:59] Unable to get VC public key configuration : invalid character '<' looking for beginning of value 2023-04-17T13:04:54.017Z fatal wcp [gcauth/gc_auth.go:47] Unable to get VC public key configuration : invalid character '<' looking for beginning of value You can see the case of an SSO domain by using the following command: /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name localhost . Example output of the above command might be VSPHERE.LOCAL . This issue is resolved in this release.
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1b-release-notes.html
Click on a version to see all relevant bugs
VMware vCenter 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.