Producent oprogramowania do wirtualizacji VMware opublikował aktualizację dla produktu vCenter Server o oznaczeniu 6.7 3s. Nowa wersja rozwiązuje problemy m.in z vSphere z zainstalowaną infrastrukturą Cisco Application Centric Infrastructure, kopiowaniem plików NFC w środowisku IPv6, możliwością zmiany polityki storage vSAN przy włączonych maszynach wirtualnych.
Co nowego?
- vCenter Server 6.7 Update 3s provides the following security updates:
- cURL is updated to version 7.84.0.
- The Apache Tomcat server is updated to version 8.5.81.
- The XStream library is updated to version 1.4.19.
- The OpenSSL library is updated to version openssl- 1.0.2zf.
- The Expat XML parser is updated to version 2.4.8.
- The Sqlite database is updated to version 3.39.0.
- Jackson is updated to version 2.12.7/2.13.2.
- Jackson-databind is updated to version 2.12.7/2.13.2.2.
- Eclipse Jetty is updated to version 9.4.48.v20220622.
- The struts2-core library is updated to version 6.0.0.
- The Oracle (Sun) JRE and JDK package is updated to version 1.8.0.341.
Rozwiązane problemy:
Networking Issues
- In vSphere environments with Cisco Application Centric Infrastructure (ACI) installed, the vpxd service might become unresponsiveIn vSphere environments with Cisco Application Centric Infrastructure ACI installed, the vpxd service might not properly handle ESXi host local ports and become unresponsive. In the
vpxd.log, you see errors such as:ODBC error: (22003) - ERROR: numeric field overflow;.This issue is resolved in this release.
Miscellaneous Issues
- NFC file copy operations intermittently fail in an IPv6 environmentDuring NFC copy in IPV6 environment, if IPv6 addresses in the
NFC Copy Specfor the source and destination contain uncompressed sequence of zeroes, the spec validation fails because IPv6 addresses do not match with that of the hosts stored values. As a result, the NFC copy and the operation that invoked the NFC copy fail. For example, when you attempt to deploy a template from Content Library. The issue does not affect IPv4 environments.This issue is resolved in this release.
- After update to vCenter Server 6.7 Update 3r, the vpxd service might not start due to lack of disk space, caused by content-library-runtime.log.stdout logsAfter update to vCenter Server 6.7 Update 3r, you might see logs in the
content-library-runtime.log.stdoutfile to grow quickly and cause space shortage in the drive of your vCenter Server installation. As a result,vpxd.cfgmight not function properly and the vpxd service cannot start, which makes vCenter Server unresponsive.The issue is resolved in this release.
vSAN Issues
- You cannot change the vSAN storage policy of powered-on virtual machinesIf a powered-on VM has a virtual IDE controller, the hostd service prevents any changes to the device on that controller, including changes in the vSAN storage policy. As a result, when you try to change the storage policy of such a VM, the operations fails with a message in the vSphere Client such as:
The attempted operation cannot be performed in the current state ("Powered on").This issue is resolved in this release. The fix makes sure that powered-on VM with an IDE disk can be reconfigured with a new storage policy.
vMotion Issues
- After a migration operation, Windows 10 virtual machines might fail with a blue diagnostic screen and reports for a microcode revision mismatchAfter a migration operation, Windows 10 virtual machines might fail with a blue diagnostic screen and report a microcode revision mismatch error such as:
- MICROCODE_REVISION_MISMATCH (17e)
The issue occurs when a scan of the CPUs runs during the migration operation and the firmware of the source CPUs does not match with the firmware of the destination CPUs.This issue is resolved in this release.
Networking Issues
- VM clone fails with an error and newly created dvPort remains in vCenter Server databaseIf a virtual machine clone spec has the
guestinfo.resync.mac.addrkey in theextraConfigelements, such as the following:
<ovf:Info>Virtual hardware requirements</ovf:Info><vmw:ExtraConfig vmw:key="guestinfo.resync.mac.addr"/>, a cloning operation might fail, because in some cases, a value for the key might not pass and remain unset. In the vpxd logs, you see with an error such as vmodl.fault.InvalidArgument and error messages like „A specified parameter was not correct: config.extraConfig[„guestinfo.resync.mac.addr”]”. As a result, the newly created dvPort for the failed clone remains unused in the vCenter Server database.This issue is resolved in this release. The fix makes sure to remove unused dvPort from the vCenter Server database. If the error persists, you must remove the
guestinfo.resync.mac.addrkey in theextraConfigelements or set a valid MAC address as value.
Notatki producenta: VMware vCenter Server 6.7 Update 3s Release Notes
Pozdrawiamy,
Zespół B&B
Bezpieczeństwo w biznesie