Loading...
Loading...
A custom bug ID has been generated as the vendor did not provide one: cd9e3cdc770d Known affected version(s) that were inferred because the vendor did not provide any: 7.0.3.01300
After a cluster upgrade, when vCenter restarts, in a short time most of the VMs might be migrated to a small group of the ESXi hosts in the cluster, which leads to a performance downgrade. In the FDM Install error logs on the ESXi hosts, you see a warning such as rm: can't remove '/tardisks/vmware_f.v00': Device or resource busy . After a cluster upgrade, while ESXi hosts reconnect to the vpxd service, the Fault Domain Manager (FDM) agent needs some time to become fully operational. If during this time the vSphere DRS component that scans the VM-to-host compatibility finds the FDM agent does not work on a given ESXi host, DRS forces the migration of the VMs to another host for high availability purposes. This issue is resolved in this release. The fix adds a new grace period mechanism where DRS waits for 10 minutes until migrating VMs out of their current ESXi host, because of the transient compatibility failure. You can configure this grace period by using the advanced option CompatCheckTransientFailureTimeSeconds , following this sample: IOPT(COMPAT_CHECK_TRANSIENT_FAILURE_TIME_SECS, "CompatCheckTransientFailureTimeSeconds", "Length of time a same host compatibility check failure is tolerated. " "(-1 -> ignore same host compatibility check failure)", -1, 3600, 600)
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
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.