Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: 15cb0d5e9787 Known affected version(s) that were inferred because the vendor did not provide any: 8.0.0.10100
When you use a REST API function such as /rest/vcenter/vm/{vm-id} , the call might fail with an error message such as Internal server error: Error: Http error 500 while requesting '/rest/vcenter/vm/vm-xx’ . The issue occurs because the networkBootProtocol value might not persist in the vCenter Server database after reconfiguring the VM. As a result, when vCenter Server restarts, the networkBootProtocol value is not available and the function /rest/vcenter/vm/{vm-id} fails. This issue is resolved in this release. The fix makes sure that the fixed now and the networkBootProtocol value persists in the vCenter Server database after a VM reconfigure and vCenter Server restart.
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.