Producent oprogramowania do wirtualizacji Vmware, udostępnił następną aktualizacje dla vCenter Server o oznaczeniu 7.0 Update 3c. Dzięki nowej aktualizacji, producent naprawił dotychczasowe błędy tworzenia kopii zapasowych serwera. Ponadto naprawiono problem z wykorzystywaniem protokołu SMB do tworzenia kopii. Problem z tworzeniem i synchronizacją klastrów vSphere został poprawiony, również ze względów zmiany sterowników producenta Intel można było napotkać wiele błędów. Po aktualizacji ten problem został naprawiony, lecz w przypadku dalszych błędów producent opublikował skrypt, który ma na celu naprawę problemu z dwoma sterownikami. Po więcej szczegółowych informacji, zapraszam do dalszej części artykułu.
Co nowego :
- Ze względu na niedawną zmianę sterownika producenta Intel i40en na i40en, hosty ESXi w niektórych środowiskach starszych niż ESXi 7.0 Update 2a mogą mieć obie wersje sterowników, co skutkuje kilkoma problemami. Problemy zostały rozwiązane w vSphere 7.0 Update 3c ale firma VMware udostępnia skrypt „vSphere_upgrade_assessment.p”, którego można użyć do zidentyfikowania hostów ESXi wymagających naprawy przed rozpoczęciem uaktualniania serwera vCenter Server.
Rozwiązane problemy:
Backup and Restore Issues
- File-based backup of vCenter Server fails with a DB UNHEALTHY error in the vCenter Server Management InterfaceYou might see the error
DB UNHEALTHYin the vCenter Server Management Interface while setting a file-based backup of a vCenter Server instance due to some expected changes in the DB schema that the vSAN health service might wrongly consider a health issue.This issue is resolved in this release. For more information, see VMware knowledge base article 86084.
- vCenter Server backup fails with an error about an underlying process statusWhen you attempt to backup your vCenter Server system, the operation might fail with a message in the vSphere Client such as
Error during component wcp backup Underlying process status. rc: 1. The issue occurs when the vCenter Server PNID cannot resolve due to HTTP or HTTPS proxy settings.This issue is resolved in this release.
- If you use SMB as backup protocol, vCenter Server backup fails with the error Path not exported by the remote filesystemAs a side effect of the default enablement of the Federal Information Processing Standards (FIPS) in vCenter Server 7.0 Update 3, if you use SMB as the backup protocol, vCenter Server backup fails. In the vSphere Client, you see the error
Path not exported by the remote filesystem.This issue is resolved in this release. For more information, see VMware knowledge base article 86069.
- Multiple vCenter Servers might become unresponsive due to a memory leak in the VMware Service Lifecycle Manager databaseA memory leak issue with the database of the
vmware-vmonservice, which manages the lifecycle of vCenter Server, might cause multiple vCenter Server instances to become unresponsive. In the vSphere Client, you see an error such as:
Error: [500] An error occurred while fetching identity providers. Try again. If problem persists, contact your administrator
In the vpxd logs, you see an error such as:
Failed to get exclusive locl: ODBC error, ERROR : Failed Lock.This issue is resolved in this release.
Installation, Upgrade and Migration Issues
- Enabling vSphere HA might fail or never complete on ESXi hosts of version later than 7.0 Update 2aDue to the recent name change in the Intel i40en driver to i40enu and back to i40en, ESXi hosts in some environments later than ESXi 7.0 Update 2a might have both driver versions, which results in several issues, including vSphere HA failure. vSphere HA might not be successfully enabled on newly added or moved hosts of versions ESXi 7.0 Update 3a, 7.0 Update 3, 7.0 Update 2d, and 7.0 Update 2c.
This issue is resolved in this release.
- ISO and URL-based patching from vCenter Server 7.0 Update 3 to vCenter Server 7.0 Update 3a might fail due to unsuccessful update of the completion statusPatching your vCenter Server system from vCenter Server 7.0 Update 3 to vCenter Server 7.0 Update 3a by using an ISO or a repository URL might fail, because a stage complete status is not available. In the vCenter Server Management Interface, you see an error such as
Package discrepancy error, Cannot resume!. If you use CLI, you see errors such asStage path file doesn't existandStaging failed. Retry to resume from the current state. Or please collect the VC support bundle.
The issue occurs because a file integrity check might stop a stage in the patching flow. After the check, the patch operation continues and completes successfully, but the stage complete status fails to update.This issue is resolved in this release.
- Upgrade from vCenter Server 7.0 Update 2 to vCenter Server 7.0 Update 3 fails with a VMware Postgres errorWhen you upgrade a single vCenter Server instance from version vCenter Server 7.0 Update 2 to vCenter Server 7.0 Update 3, the upgrade might fail due to an issue with the
pg_addonsextension that affects the VMware Postgres database.In the
pg_upgrade_server.logfile, you see logs such asERROR: could not find function "archive_build_segment_list" in file "/opt/vmware/vpostgres/13/lib/pg_addons.so.This issue is resolved in this release. For more information, see VMware knowledge base article 86073.
- vCenter Server 7.0 Update 3c delivers the following security updates:
- The Spring package in the vSphere Client is updated to version 5.2.4.
- Apache Struts is updated to version 2.5.28.3.
- vCenter Server 7.0 Update 3c updates Apache httpd to address CVE-2021-40438. VMware would like to thank Saeed Kamranfar of Sotoon Security for alerting on this issue.
- Apache log4j is updated to version 2.17 to resolve CVE-2021-44228 and CVE-2021-45046. For more information on these vulnerabilities and their impact on VMware products, please see VMSA-2021-0028.
Zapraszam do notatek producenta: VMware vCenter Server 7.0 Update 3c
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie