check-circle-line exclamation-circle-line close-line

vCenter Server 6.5 Update 3f | DEC 19 2019 | ISO Build 15259038
vCenter Server Appliance 6.5 Update 3f | DEC 19 2019 | ISO Build 15259038

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

The vCenter Server 6.5 Update 3f release includes the following list of new features.

Earlier Releases of vCenter Server 6.5

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 6.5 are:

For internationalization, compatibility, installation and upgrades, product support notices, and features see the VMware vSphere 6.5 Release Notes.

Patches Contained in This Release

This release of vCenter Server 6.5 Update 3f delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Security Patch for VMware vCenter Server 6.5 Update 3f

Third Party Product fixes (for example: JRE, tcServer). This patch is applicable for vCenter Server for Windows, Platform Services Controller for Windows, and vSphere Update Manager.

For vCenter Server and Platform Services Controller for Windows

Download Filename VMware-VIMPatch-T-6.5.0-15259038.iso
Build 15259038
Download Size 40.9 MB
md5sum f85525354056ac3e2b484f0847348c24
sha1checksum 286f4829ff09a9da330671cb5b4ba15aafa0e34e

These vCenter Server components depend on JRE and have to be patched:

  • vCenter Server
  • Platform Services Controller
  • vSphere Update Manager

Download and Installation

You can download this patch by going to the VMware Patch Download Center and selecting VC from the Select a Product drop-down menu. 

  1. Mount the VMware-VIMPatch-T-6.5.0-15259038.iso to the system where the vCenter Server component is installed.  
  2. Double-click  ISO_mount_directory/autorun.exe.
  3. In the vCenter Server Java Components Update wizard, click Patch All.

Full Patch for VMware vCenter Server Appliance 6.5 Update 3f

Product Patch for vCenter Server Appliance 6.5 containing VMware software fixes, security fixes, and Third Party Product fixes (for example: JRE and tcServer).

This patch is applicable to the vCenter Server Appliance and Platform Services Controller Appliance.

For vCenter Server and Platform Services Controller Appliances

Download Filename VMware-vCenter-Server-Appliance-6.5.0.32000-15259038-patch-FP.iso
Build 15259038
Download Size 1708.4 MB
md5sum 6d1c346c84475e83d4232b06cacb1da3
sha1checksum 26c0191c356dfd602ea9563a728264bf37e24eeb

Download and Installation

You can download this patch by going to the VMware Patch Download Center and selecting VC from the Select a Product drop-down menu.

  1. Attach the VMware-vCenter-Server-Appliance-6.5.0.32000-15259038-patch-FP.iso​​ file to the vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell as root and run the commands given below:
    • To stage the ISO:

      software-packages stage --iso

    • To see the staged content:

      software-packages list --staged

    • To install the staged rpms:

      software-packages install --staged

For more information on patching the vCenter Server Appliance, see Patching the vCenter Server Appliance.

For more information on staging patches, see Stage Patches to vCenter Server Appliance.

For more information on installing patches, see Install vCenter Server Appliance Patches.

For issues resolved in this patch see Resolved Issues.

For Photon OS updates, see VMware vCenter Server Appliance Photon OS Security Patches

For more information on patching using the Appliance Management Interface, see Patching the vCenter Server Appliance by Using the Appliance Management Interface.

Upgrade Notes for This Release

Important: Upgrades and migrations from vCenter Server 6.5 Update 3f to vCenter Server 6.7 Update 3 and above are not supported. For more information on vCenter Server supported upgrade and migration paths, please refer to VMware knowledge base article 67077.

Upgrades or migration of vCenter Server earlier than 5.5 Update 3b when the environment is with an external vCenter Single Sign-On to vCenter Server 6.5 Update 3f with an external Platform Services Controller are unsupported. For example, to upgrade or migrate vCenter Server 5.5 with an external vCenter Single Sign-On to vCenter Server 6.5 Update 3f with an external Platform Services Controller, you must first update to vCenter Server 5.5 Update 3b and then perform the upgrade or migration to vCenter Server 6.5 Update 3f.

vCenter Server 5.5 Update 3b build numbers are:

  • vCenter Server 5.5 Update 3b, build 3252642
  • vCenter Server Appliance 5.5 Update 3b, build 3255668

Upgrades or migration of vCenter Server 5.5 and later with an embedded vCenter Single Sign-On to vCenter Server 6.5 Update 3f with an embedded Platform Services Controller are supported scenarios.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • Update to VMware PostgreSQL

    VMware PostgreSQL is updated to version 9.4.24.

  • Update to the Spring Framework

    The Spring Framework is updated to version 4.3.25.

  • Update to the Expat XML parser

    The Expat XML parser is updated to version 2.2.9.

  • Update of the SQLite database

    The SQLite database is updated to version 3.29.0.

  • Update to Simple Logging Facade for Java (SLF4J)

    The SLF4J package is updated to version 1.7.28.

  • Update of the Jackson package

    The Jackson package is updated to version 2.9.10. 

  • Update to the Apache Commons Collections

    The Apache Commons Collections is updated to version 3.2.2.

  • Update to the Apache Tomcat server

    The Apache Tomcat server is updated to version 8.5.47.

  • You cannot add a Key Management Server to a vCenter Server Appliance by using an FQDN in a pure IPv6 environment

    In a pure IPv6 environment, adding a Key Management Server to a vCenter Server Appliance by using an FQDN might result in an error such as cannot retrieve the requested certificate. Adding a Key Management Server by using an IPv6 address works.

    This issue is resolved in this release.

  • Update to JRE

    Oracle (Sun) JRE is updated to version 1.8.221.

  • When reconfiguring a virtual machine, a user without the Virtual machine.Configuration.Advanced configuration privilege can set the latency sensitivity of the target virtual machine

    The operation to reconfigure a virtual machine allows a user to set the latency sensitivity attribute of a virtual machine. The operation does not correctly validate if the user requesting the operation has the required Virtual machine.Configuration.Advanced configuration privilege to modify the latency sensitivity setting of the virtual machine.

    This issue is resolved in this release.

  • Update to OpenSSL

    The OpenSSL package is updated to version openssl-1.0.2t.

  • You cannot log in to the vSphere Client by using an RSA SecurID

    If the external Active Directory identity source is configured as Integrate Windows Authentication and RSA is using an LDAP attribute other than UPN for the User ID, you cannot log in to the vSphere Client.

    This issue is resolved in this release.

  • Update to the International Component for Unicode for Java (ICU4J) library

    The ICU4J library is updated to version 64.2.

  • Update to cURL

    cURL in the vCenter Server Appliance is updated to 7.66.0.

  • Update to Apache Log4j Core

    The Apache Log4j Core 2.8.x branch is updated to 2.8.2 and the 1.2.x branch to 1.2.17.

  • Update to Apache Commons BeanUtils

    Apache Commons BeanUtils is updated to version 1.9.4.

Storage Issues
  • vSphere Storage DRS fails to generate enough migrations with vSphere vMotion during ExpandDisk operations and the reconfiguration for the virtual machine fails

    During ExpandDisk operations, vSphere Storage DRS recommends the migration of some of the existing virtual machines or disks to another datastore to free resources for the new requested capacity. However, vSphere Storage DRS does not include some of the Storage vMotion actions in the final recommendation. As a result, only a part of the required resources are freed up on the current datastore on which the disk is expanded, and the ExpandDisk operation fails with a NoDiskSpace error.

    This issue is resolved in this release.

vMotion Issues
  • Virtual machine migration operations, such as instant clone provisioning, might fail due to a race condition

    Due to a rare condition between operations that create a namespace database with solutions such as VMware AppDefense, and migration of virtual machines by using Storage vMotion or the Enhanced vMotion Compatibility, the migration might fail.

    This issue is resolved in this release.

  • After migration of virtual machines by using vSphere Storage vMotion, the virtual machine Summary tab might not display updated storage usage field

    When changing datastores, if the storage policy or thin provisioning values are different, the disk space used could change. After migration of virtual machines by using Storage vMotion, the virtual machine Summary tab in either the vSphere Web Client or vSphere Client might not display the updated storage usage field.

    This issue is resolved in this release.

Upgrade Issues
  • Upgrade fails without a notification due to insufficient space in the default partition of the source machine

    During upgrade, when you specify the type of configuration data to be copied from the source vCenter Server instance to the target vCenter Server instance, if the source machine has insufficient space in the default partition to gather the configuration data, the upgrade fails. However, you see no error or notification message about the insufficient space.

    This issue is resolved in this release. If no enough space is available in the default partition, in the Connect to source vCenter Server step from Stage 2 of the upgrade wizard, you must specify an export directory on the source machine.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • In the vSphere Web Client, you cannot set the CPU limit for virtual machines to Unlimited

    When you deploy virtual machines or edit the settings of virtual machines in the vSphere Web Client, the option Maximum: Unlimited that sets the CPU limit for virtual machines to unlimited is not available.

    This issue is resolved in this release. To use the option Maximum: Unlimited in the vSphere Web Client, right-click a virtual machine and click Edit Settings. In the Virtual Hardware tab, navigate to CPU > Limit and from the drop-down menu select Maximum: Unlimited

  • You see some events with syslog severity level Error, when severity is not set, while the API reports the severity as Info

    In the vCenter Client or vSphere Web Client, when severity is not set, you might see events with syslog severity level Error, while the API reports the severity as Info. In the syslog server, you might receive messages and SNMP traps such as:
    12483 - - Event [1054] [1-1] [2019-11-18T12:51:27.340927Z] [vim.event.EventEx] [error] [] [vcqaDC] [1054] [Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic2 is down. Affected portgroups:"Management Network".]
    or
    12483 - - Event [3122] [1-1] [2019-11-20T12:15:12.678749Z] [vim.event.EventEx] [error] [] [vcqaDC] [3122] [Alarm 'Host connection failure' on 10.160.84.34 triggered by event 3119 'Host 10.160.84.34 in vcqaDC is not responding']
    or
    12483 - - Event [4114] [1-1] [2019-11-21T09:47:50.246129Z] [vim.event.EventEx] [error] [] [vcqaDC] [4114] [Alarm 'Cannot connect to storage' on 10.160.90.127 triggered by event 4112 'Lost connection to server 10.160.93.11 mount point NFS-10.160.93.11 mounted as e49f9aaf-aaa8c2a1-0000-000000000000 (/store).']

    This issue is resolved in this release.

Server Configuration Issues
  • Random core dumps of the netlogond daemon pile up in the /storage/core directory

    An invalid memory copy operation might trigger intermittent core dumps of the netlogond daemon. As a result, core dumps fill up the /storage/core directory.

    This issue is resolved in this release.

Miscellaneous Issues
  • You cannot add or move ESXi hosts into a cluster with enabled Proactive High Availability (HA)

    If you add or move an ESXi host to a cluster with enabled Proactive HA, and if the host is not part of health monitoring, the operation might fail with an error, such as NotSupported.

    This issue is resolved in this release. The fix allows adding and moving ESXi hosts into clusters with enabled Proactive HA. If the host is not part of health monitoring at the time of joining the cluster, vSphere DRS treats it as in quarantine with a state Unknown.

Virtual Machine Management Issues
  • When you deploy a virtual machine with a VMXNET3 virtual network device from a template, the DirectPath I/O option is checked by default

    In the vSphere Web Client, when you deploy a virtual machine with a VMXNET3 virtual network device from a template, the DirectPath I/O might be checked even if the option was not active in the virtual machine from which you created the template.

    This issue is resolved in this release. 

  • BIOS UUID of virtual machines present in the OVF file while exporting an OVF template

    You might see the BIOS UUID of a virtual machine automatically included in the OVF file while exporting an OVF template.

    This issue is resolved in this release.

  • If the virtual machine memory property config.memoryReservationLockedToMax is set to TRUE, but summary.config.memorySizeMB is not defined, the vpxd service and failovers by using vCenter Server High Availability might fail

    If the virtual machine memory property config.memoryReservationLockedToMax is set to TRUE and summary.config.memorySizeMB is not defined, the vpxd service and failovers by using vCenter Server High Availability might fail. The issue is observed when the vpxd service tries to get the property value and it is not set, or when you run VMware vCloud Suite queries referring to the virtual property reservationMemoryForVM. If config.memoryReservationLockedToMax is not set, or is set to FALSE, the summary.config.memorySizeMB property is not required and the vpxd service does not crash.

    This issue is resolved in this release. For older versions, make sure the summary.config.memorySizeMB property is defined if config.memoryReservationLockedToMax is set to TRUE.

  • vSphere Storage DRS might fail to handle some incorrect input specifications and the vpxd service becomes unresponsive

    If vSphere Storage DRS fails to handle some incorrect input specifications, the vpxd service might fail or become temporary unresponsive. You might see a backtrace such as at bora/vpx/drs/interface/drmStorageResourceManager.cpp:5608 in the vpxd dump.

    This issue is resolved in this release.

  • If vSphere Storage DRS is enabled with Storage I/O Control, the vpxd service might occasionally fail

    If vSphere Storage DRS is enabled with Storage I/O Control, the vpxd service might occasionally fail due to a NULL pointer dereference.

    This issue is resolved in this release.

  • If you set the memory limit to 0 MB when cloning or deploying a virtual machine from a template, the vCenter Server system might become temporarily unresponsive

    If you set the memory limit to 0 MB by using the vSphere Client or the vSphere Web Client when cloning or deploying a virtual machine from a template, the vCenter Server system might become temporarily unresponsive. Other production virtual machines might require a restart to recover.

    This issue is resolved in this release. The fix removes the 0 MB value from the Memory drop-down menu in the vSphere Client or the vSphere Web Client.

Known Issues

The known issues are grouped as follows.

Convergence Issues
  • Convergence of a vCenter Server Appliance with an external Platform Services Controller to a vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode fails after the first node is converged

    Converging vCenter Server Appliance with an external Platform Services Controller instances to vCenter Server Appliance with an embedded Platform Services Controller instances connected in Embedded Linked Mode might fail after the first node is converged, because during the convergence, the VMware Directory Service (vmdir) is set in standalone mode. As a result, the convergence of the subsequent vCenter Server nodes fails.

    Workaround: For more information, see VMware knowledge base article 71391.

Virtual Machine Management Issues
  • VMware Service Lifecycle Manager restarts the vpxd service every couple of days

    If you enable Storage I/O Control for a datastore with a large amount of connected ESXi hosts, a large number of I/O events might pile up for handling by the vpxd service. In such a case, the VMware Service Lifecycle Manager might restart the vpxd service.

    Workaround: Disable Storage I/O Control for datastores with a large amount of connected ESXi hosts or reduce the number of connected hosts.

Known Issues from Earlier Releases

To view a list of previous known issues, click here.