Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: 929e708facb2 Known affected version(s) that were inferred because the vendor did not provide any: 8.0.0.10100
If a virtual machine clone spec has the guestinfo.resync.mac.addr key in the extraConfig elements, such as the following: <ovf:Info>Virtual hardware requirements</ovf:Info><vmw:ExtraConfig vmw:key="guestinfo.resync.mac.addr"/> , a cloning operation might fail, because in some cases, a value for the key might not pass and remains unset. In the vpxd logs, you see with an error such as vmodl.fault.InvalidArgument and error messages like A specified parameter was not correct: config.extraConfig["guestinfo.resync.mac.addr"]" . As a result, the newly created dvPort for the failed clone remains unused in the vCenter Server database. This issue is resolved in this release. The fix makes sure to remove unused dvPort from the vCenter Server database. If the error persists, you must remove the guestinfo.resync.mac.addr key in the extraConfig elements or set a valid MAC address as value.
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.