Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: 674cf471c833 Known affected version(s) that were inferred because the vendor did not provide any: 7.0.3.01600, 8.0.0.10100
Starting from vCenter Server 8.0.b, if you use vSphere Automation API, Certificate Manager utility, or certificate management CLIs as an interface to manage vCenter Server certificates, you can leave the organizationalUnitName field empty. The change does not affect existing workflows for certificate replacement or Certificate Signing Requests (CSRs). The vSphere Client and PowerCLI 12.4 still require data for the organizationalUnitName field. This issue is resolved in this release.
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3o-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
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.