Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: 76d55daee1cb Known affected version(s) that were inferred because the vendor did not provide any: 7.0.3.01300, 8.0.0.10100
If you use IWA for vCenter Server authentication, the STS service might fail during attempts to log in to the vCenter Server system, because the Active Directory might return a null LDAP hostname. Logins fail until the STS service restarts. The vMonCoredumper.log file contains entries similar to the following: 2022-12-29T07:16:15.305Z In(05) host-12345 Notify vMon about pool-2-thread-4 dumping core. Pid : 3315 2022-12-29T07:16:15.320Z In(05) host-12345 Successfully notified vMon. 2022-127-29T07:16:16.785Z In(05) host-12345 Successfully generated core file /var/core/core.pool-2-thread-4.3315. The hs_err_sts_pid*.log file contains entries such as: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f4d80203d06, pid=3315, tid=0x00007f4ce3d1f700 This issue is resolved in this release. Due to performance issues with IWA-based authentication, vSphere 8.0 deprecates the use of IWA. You can use AD over LDAP or ADFS.
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3l-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80b-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.