Loading...
Loading...
Known affected version(s) that were inferred because the vendor did not provide any: 8.0.3.00700
In rare cases, vCenter might become unresponsive to incoming requests due to a deadlock in the HTTP/2 stack of the vmacore library that might eventually block all available worker threads. vCenter services do not immediately fail, but running tasks and API calls start hanging or timing out. This issue is resolved in this release. If you have implemented the workaround from KB 424166 , you can revert the changes for all vCenter services to which you have applied it. For example, for the vpxd service, run the command python /usr/lib/vmware-vpx/py/xmlcfg.py -f /etc/vmware-vpx/vpxd.cfg delete vmacore/http/http2/maxPooledStreams in the vCenter Appliance and restart the vpxd service with the command service-control --restart vpxd .
https://knowledge.broadcom.com/external/article/424166
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u3i-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.