Producent oprogramowania VMware opublikował najnowszą aktualizację dla vCenter Server 8.0 Update 2a. Aktualizacja rozwiązuje problem z zastosowaniem licencji vSAN do dwuwęzłowego klastra vSAN, rozwiązano problem z błędem „Failed to perform Cleanup” podczas patchowania vCenter Server do wersji 8.0 U2 oraz błąd który powodował rozłączenie hostów ESXi z serwera vCenter.
Rozwiązane problemy:
vSAN Issues
-
Cannot apply vSAN standard license to a vSAN two-node cluster after upgrade
After you upgrade a vCenter system to version 8.0 Update 2, the vSAN evaluation license is applied to vSAN clusters. If you attempt to apply a vSAN standard license to a vSAN two-node cluster, you might see the following error: The license does not support some of the features that assets currently use. This issue occurs because the stretched cluster feature is reported as in-use state for vSAN two-node clusters.
This issue is resolved in this release.
Install, Upgrade and Migration Issues
-
A set of VMDKs might get associated to incorrect mount points in a vCenter instance
In very rare cases, the Linux kernel might associate an incorrect size of the mount point for some VMDKs in a vCenter instance. You see the issue when you run the
lsblkcommand and compare the result with the default disk layout for vCenter. For example, the default size for a /storage/seat mount point for a vCenter of medium deployment size is expected to be 50GB and for /storage/netdump is 10GB, but after running thelsblkcommand, you might see these sizes reversed, or 10GB for the /storage/seat mount point and 50GB for /storage/netdump. The issue might affect any number or sequence of VMDKs. The issue occurs during a vCenter deployment and might result in failure of backup and restore operations.This issue is resolved in this release.
-
You see an error „Failed to perform Cleanup” during patching to vCenter Server 8.0 Update 2
The Logical Volume Manager (LVM) might take longer than the 4 min time out for cleanup operations during an update to vCenter 8.0 Update 2. As a result, in the vSphere Client you see the error Failed to perform Cleanup. The update operation completes successfully, but some post-update tasks fail.
This issue is resolved in this release. The fix increases the timeout to 30 min.
-
Upgrade or fresh installation of vCenter 8.0 Update 2 might fail during the start of the vc-ws1a-broker service
During an upgrade or installation of vCenter 8.0 Update 2, if a DNS server in your network is offline or not configured correctly, during the start of the vc-ws1a-broker service, which enables new identity providers such as Microsoft EntraID and Okta, the PostgreSQL database connection process might time out. As a result, the service fails to start, and the upgrade or installation job is not successful.
This issue is resolved in this release.
Server Configuration Issues
-
After update or upgrade to vCenter Server 8.0 Update 2, ESXi hosts disconnect from vCenter
In rare cases, when a vCenter holds a legacy non-CA certificate in its TRUSTED_ROOTS store, after an upgrade or update to 8.0 Update 2, the hostd service filters out such certificates and certain ESXi hosts cannot reconnect to this vCenter. Attempts to manually add such hosts to the vCenter system also fail.
This issue is resolved in this release.
Installation, Upgrade, and Migration Issues
-
You see a security warning for the ESX Agent Manager configuration during the pre-check phase of a vCenter upgrade
During the pre-check phase of a vCenter update or upgrade, in the vSphere Client and logs, you might see an error such as:
Source ESX Agent Manager Configuration contains URLs that are not trusted by the System! Please refer to https://kb.vmware.com/s/article/93526 to trust the URLs: <LIST_OF_URLs>Or
Source vSphere ESX Agent Manager (EAM) upgrade failed to obtain EAM URLs to check against trusted certificates by the System! Verify that the ESX Agent Manager extension is running properly on the source vCenter Server instance and https://VC_IP/eam/mob presents correct data. If log in to the MOB is not successful, try resolving the issue with https://kb.vmware.com/s/article/94934. -
vCenter upgrade or update to 8.0 Update 2a or later fails during precheck with the error „VMCA root certificate validation failed”
If your vCenter system has a legacy VMCA root certificate dating back to version 5.x which does not have the Subject Key Identifier (SKID) extension, upgrades and updates to vCenter 8.0 Update 2 and later fail because the OpenSSL version 3.0 in 8.0 Update 2 is not compatible with legacy root certificates. vCenter Server 8.0 Update 2a adds a precheck to detect this issue and shows the error message VMCA root certificate validation failed if the source vCenter has VMCA root certificate without SKID.
Workaround: Regenerate a VMCA root certificate by following the steps in VMware knowledge base article 94840.
Notatki producenta: VMware vCenter Server 8.0 Update 2
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie