vSphere 7.0 Update 3 Known Issues - Workarounds & Fix
Article ID: 344749
Updated On:
Products
Issue/Introduction
Since the release of vSphere 7.0 Update 3 there has been the following reported issues.
Important Note:- vSphere 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.
VMware ESXi Issues
|
Summary |
KB |
Impact |
Fix / Workaround |
| ESXi 7.0 U3 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. | |
|
Enabling vSphere HA might fail or never complete on hosts that were upgraded to ESXi 7.0 U3. |
Environmental Stability |
This issue is resolved in ESXi 7.0 Update 3c. | |
|
When a host attempting to power on or vMotion Virtual Machines with Physical RDM LUNS, a condition may occur where services fail to close properly introduced in ESXi 7.0 U3, resulting in device handles incorrectly being left open resulting in "failed to lock the file" conflicts. |
Environmental Stability |
This issue is resolved in ESXi 7.0 Update 3c. | |
|
The hostd service on ESXi 7.0U3 repeatedly crashes due to memory corruption in a function that is part of the time service event monitoring (enabled by default). |
Environmental Stability |
This issue is resolved in ESXi 7.0 Update 3c. |
VMware vCenter Server Issues
|
Summary |
KB |
Impact |
Fix / Workaround |
|
Lifecycle Manager will not be available in the vSphere Client when logging into vCenter Server 7.0 U3 with Active Directory or LDAP credentials. This is not apparent when using SSO domain credentials. |
Configuration Limiting |
This issue is resolved in vCenter Server 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. | |
|
File based backups will fail when the database consistency check falsely detects that the DB is unhealthy in environments using VSAN. |
BCDR Impacting |
This issue is resolved in vCenter Server 7.0 Update 3c. | |
|
Patching vCenter Server to 7.0 U3 might fail during staging due to a stale configuration. |
BCDR Impacting |
This issue is resolved in vCenter Server 7.0 Update 3c. | |
|
File based backups will fail when the database consistency check falsely detects that the DB is unhealthy if a proxy is configured on the vCenter Server. |
BCDR Impacting |
This issue is resolved in vCenter Server 7.0 Update 3c. | |
|
Upgrading to vCenter Server 7.0 U3 will fail when a stale extension is leftover in the vPostgres database from a previous VCHA configuration. |
Upgrade Impacting |
This issue is resolved in vCenter Server 7.0 Update 3c. |
Environment
Resolution
Feedback
