vSphere 7.0 Update 3 Critical Known Issues - Workarounds & Fix
Article ID: 317893
Updated On:
Products
Issue/Introduction
Since the release of vSphere 7.0 Update 3 the following critical issues have been identified.
IMPORTANT NOTE: ESXi 7.0 U3, U3a, and U3b and vCenter 7.0 U3b are no longer available for download due to several critical issues identified in them. For information regarding this decision, Please refer to KB 86398
|
Summary |
KB |
Impact |
Fix / Workaround |
|
ESXi 7.0 Update 3 hosts can experience a PSOD when virtual machines on a VMFS6 thin disk execute UNMAP/TRIM functions. |
Potential ESXi host crash |
This issue is resolved in ESXi 7.0 Update 3c. | |
|
Starting with vSphere 7.0 Update 3, the inbox i40enu network driver for ESXi changes name back to i40en. This can result in ESXi failing to update with the error: “host returned esxupdate code –1" |
Upgrade Blocking |
This issue is resolved in ESXi 7.0 Update 3c. | |
|
In vCenter 7.0 Update 3 FIPS compliance was enabled by default; This has the impact of blocking the SMB protocol; VAMI backup fails using SMB Protocol on vCenter 7.0 U3 with the error: “Path not exported by remote file system” |
BCDR Impacting |
This issue is resolved in vCenter Server 7.0 Update 3c. | |
|
Enabling vSphere HA might fail or never complete on hosts that were upgraded to ESXi 7.0 Update 3. |
Environmental Stability |
This issue is resolved in ESXi 7.0 Update 3c. |
Environment
Additional Information
Feedback
