VMware vSphere 7.0 Update 3 вернулся!
- VMware ESXi 7.0 Update 3c Release Notes
- VMware vSphere Hypervisor (ESXi) 7.0U3c
- VMware vCenter Server 7.0 Update 3c Release Notes
- VMware vCenter Server 7.0U3c
- VMware vSAN 7.0 Update 3c
В официальном списке KB обещают, что исправлены причины отзыва:
| 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. | 86100 | 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″ | 85982 | 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” | 86069 | 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. | 86191 | Environmental Stability | This issue is resolved in ESXi 7.0 Update 3c. |
Выпустили официальный список KB, обязательный к ознакомлению и применению:
| Knowledge Base article title | Knowledge Base article link |
|---|---|
| Upgrading vCenter Server 7.0 fails during precheck with “Host(s) were found in the vCenter Inventory, that are potentially problematic for a vCenter upgrade” | KB86447 |
| Using the dual_driver_check.py script | KB87258 |
| Converting an ESXi cluster to be vLCM image managed fails in vCenter Server 7.0u3c with “The following host(s) have an ESXi version higher than ESXi 7.0 U2a and lower than ESXi 7.0 U3c” | KB87308 |
| Enabling vSphere HA might fail or never complete on hosts with ESXi 7.0u2c/u2d and 7.0u3/u3a | KB87299 |
| Critical baseline may remain Non-compliant after first remediation | KB87451 |
| Platform Configuration Error: /usr/sbin/esxupdate returned with exit status: 32″, ESXi 7.0 Upgrade fails if the environment had migrated from NSX-V to NSX-T using NSX V2T migration | KB87423 |
| Workaround Instructions For CVE-2021-22045 on VMware ESXi Hosts | KB87249 |
| Upgrading to vCenter Server 7.0 U3c using the CLI fails during precheck with “Installation failed. Retry to resume from the current state. Or please collect the VC support bundle”‘ | KB87319 |
Почему-то не упомянули в таблицах KB эти фиксы:
-
- After updating to ESXi 7.0 Update 3 Machines with Physical RDM disk can not be migrated or powered on (86158)
- VAMI backups fail with “Db health is UNHEALTHY, Backup Failed. Disable health check to take backup in current state.” (86084)
- File-Based Backup fails on vCenter Server 7.0 configured with a Proxy (86045)
- Update from vCenter 7.0 Update 3 to U3a fails with “Stage path file doesn’t exist” or “Package discrepency error, Cannot resume!” (86159)
- vCenter upgrade from 7.0 update 2 to update 3.0 fails with could not find function “archive_build_segment_list” in file “/opt/vmware/vpostgres/13/lib/pg_addons.so” (86073)
- Workaround instructions to address CVE-2021-44228 and CVE-2021-45046 in vCenter Server and vCenter Cloud Gateway (87081)
