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

vCenter Server 6.0 Update 3j | SEP 12 2019 | ISO Build 14518058

vCenter Server Appliance 6.0 Update 3j | SEP 12 2019 | ISO Build 14518058

vCenter Server 6.0 Update 3j on vCenter Server Appliance Build 14510547

vCenter Server 6.0 Update 3j on Windows Build 14510545

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.0 Update 3j release addresses issues documented in the Resolved Issues section.

Earlier Releases of vCenter Server 6.0

For compatibility, installation and upgrades, product support notices, and features see the VMware vCenter Server 6.0 Update 3 Release Notes.

Patches contained in this release

vCenter Server 6.0 Update 3j delivers the following patch. See the VMware Patch Download Center for more information on downloading patches.

Security Patch for VMware vCenter Server 6.0 Update 3j

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.

NOTE: This patch updates only the JRE version 1.7.0_231.

For vCenter Server and Platform Services Controller for Windows

Download Filename VMware-VIMPatch-6.0.0-14349955-20180726.iso
Build 14349955
Download Size 87.6 MB
md5sum 1a18903e1f6e4840b106367de29bec81
sha1checksum 85d5e2381f901d8e9123cac6557e245ca0e9f8b9

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

  • Platform Services Controller
  • vSphere Update Manager
  • vCenter Server

Download and Installation

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

  1. Mount the VMware-VIMPatch-6.0.0-14349955-20180726.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.0 Update 3j

Product Patch for vCenter Server Appliance 6.0 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.0.0.31000-14518061-patch-FP.iso
Build 14518061
Download Size 1814.7 MB
md5sum 7fe30feebdd1ddcca218a57919360da0
sha1checksum 312d92b675b3b355bc84dc901beec55bbc8556ac

Download and Installation

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

  1. Attach the VMware-vCenter-Server-Appliance-6.0.0.31000-14518061-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 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: Upgrade and migration paths from vCenter Server 6.0 Update 3j to vCenter Server 6.5 and 6.7 are not supported.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • Update to the Apache Tomcat server

    The Apache Tomcat server is updated to version 8.5.42.

  • Update to cURL

    cURL in the vCenter Server Appliance is updated to version 7.64.1.

  • Update of the Jackson package

    The Jackson package is updated to version 2.9.9.

  • Update to OpenSSL

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

  • Upgrade of Eclipse Jetty

    Eclipse Jetty is updated to version 9.2.28.v20190418.

  • Update to the Spring Framework

    The Spring Framework is updated to version 4.3.24.

  • Update to SUSE Linux Enterprise Server 11 SP4

    SLES 11SP4 Linux kernel is updated to resolve security issues with identifiers CVE-2019-11477, CVE-2019-11478, and CVE-2019-11479.

  • Update to the Spring Data Commons package

    The Spring Data Commons package is updated to version 1.13.22.

  • Update to the Python library

    The Python third-party library is updated to version 2.7.16.

  • Update to the NTP daemon

    The NTP daemon is updated to version 4.2.8p13.

  • Update to Apache Struts framework

    The Apache Struts framework is updated to version 2.5.20 to resolve security issues with identifiers CVE-2018-1327 and CVE-2017-12611.

  • Update to JRE

    Oracle (Sun) JRE is updated to version 1.7.0_231.

  • Update to the libxml2 library

    The ESXi userworld libxml2 library is updated to version 2.9.9.

  • Update to PostgreSQL

    PostgreSQL is updated to version 9.3.25.

Miscellaneous Issues
  • A VMware Enhanced vMotion Compatibility (EVC) cluster might not show new CPU IDs if you add a host in maintenance mode

    If you create an empty EVC cluster and add a host in maintenance mode, you might not see some new CPU IDs, such as Indirect Branch Restricted Speculation (IBRS), Single Thread Indirect Branch Predictors (STIBP) and Speculative Store Bypass Disable (SSBD), exposed by that EVC cluster.

    This issue is resolved in this release.

  • An EVC cluster might show new CPU IDs such as IBPB even if you revert an ESXi host to an older version

    If you revert an ESXi host to an older version of ESXi, an EVC cluster might expose new CPU IDs, such as IBRS, STIBP and IBPB, even though the host does not have any of the features.

    This issue is resolved in this release. However, a host that does not meet the requirements of an EVC cluster does not automatically reconnect and you must remove it from the cluster.

  • vCenter Web Client tags and messages are not displayed in a human-readable form

    Tags and messages might not display in a human-readable form in the vCenter Web Client as a result of lengthy request headers. If your environment has large security tokens in the network communication, the vpxd service cannot process the request headers to get to the human-readable labels of tags and messages due to a limiter in the communication size. This fix doubles the limiter.

    This issue is resolved in this release.

  • You receive no SNMPv3 traps from a vCenter Server system

    You might not receive SNMPv3 traps even after you complete all steps to properly convey SNMPv3 traps from a vCenter Server system, because of multi-line text in the traps.

    This issue is resolved in this release. The fix changes the snmpd agent code to handle multi-line text. For more information, see VMware knowledge base article 67810.

  • The SNMP agent of a vCenter Server Appliance might report incorrect build numbers after an upgrade

    SNMP monitoring reports might contain incorrect build numbers in the human readable object sysDescr.0 after an upgrade of the vCenter Server Appliance.

    This issue is resolved in this release.

  • An ESXi host might get disconnected from a vCenter Server system when iterating on a large directory tree

    The vpxa service might fail due to excessive memory usage when iterating on a large directory tree. As a result, an ESXi host might get disconnected from a vCenter Server system.

    This issue is resolved in this release.

  • The vCenter Server daemon service vpxd might fail to start after a server reboot

    After a server reboot, while vpxd loads the inventory from the database, it performs a workload calculation based on the inventory size and the number of available CPU cores. Certain rare combinations of these inputs might lead to an incorrect calculation, causing an error that prevents the service from starting. You might see the following error: Init failed: The data being fetched is NULL at column position 0.

    This issue is resolved in this release. A previous workaround involved disabling one or more CPU cores in the vCenter Server Appliance to fix the calculation. You can undo the workaround after you install this patch.

  • TCP sessions might timeout and cause delays or loss of property collector updates

    TCP sessions might timeout and cause delays or loss of property collector updates. The fix enables the TCP Keep-Alive option for all TCP sockets in the vmacore module, which the hostd service uses as a framework for multithreaded distributed applications.

    This issue is resolved in this release. 

  • Deleting a virtual machine might cause ESXi hosts to disconnect from a vCenter Server system

    Deleting a virtual machine on an ESXi server might cause synchronization issues between the ESXi host and the vCenter Server system. As a result, the ESXi host loses connectivity to the vCenter Server system.

    This issue is resolved in this release.

  • The vpxd service fails intermittently from a couple of hours to a couple of days

    The vpxd service fails intermittently from a couple of hours to a couple of days due to a thread race in the propertyCollector service interface. Overlapping blocking calls might cause a filter that has been destroyed to be used in an update.

    This issue is resolved in this release. The fix makes sure that destroyed filters are removed from all internal containers before the next call comes in.

  • You might see a false negative error that the hostd service is not responsive

    In rare occasions, you might see a false negative error that the hostd service is not responsive. The issue does not pose a technical risk. This fix clears the error field after each SSL callback.

    This issue is resolved in this release.

  • In an environment with heavy workloads, the vmware-stsd service might go out of memory and fail, resulting in login failures

    Hardcoded heap memory size records in the setenv.sh file might override dynamically calculated memory estimates when starting the vmware-stsd service in an environment with heavy workloads. As a result, the vmware-stsd service might go out of memory and fail, which in turn results in login failures.

    This issue is resolved in this release. The fix removes hardcoded values from setenv.sh and the vmware-stsd service always gets the dynamically calculated value.

  • Cloning virtual machines might fail due to a race condition in the communication between vCenter Server and ESXi hosts

    A race condition in the communication between vCenter Server and ESXi hosts might cause remote procedure calls (RPC) to fail even after they succeed. As a result, operations such as cloning virtual machines might fail.

     This issue is resolved in this release. The fix works only for the vCenter Server Appliance and not for vCenter Server on Windows.

vMotion Issues
  • VMware vSphere Distributed Resource Scheduler might run migrations of virtual machines even when a cluster seems balanced

    In vSphere 6.0, if vSphere DRS detects in a balanced cluster an imbalance between two hosts larger than a set migration threshold, it might run some migration operations that do not effectively improve the balance between the two hosts. This fix prevents migrations of virtual machines that do not improve pairwise imbalances.

    This issue is resolved in this release. For more information, see VMware Knowledge Base article 2150667.

High Availability and Fault Tolerance Issues
  • Virtual machines might power on slowly after a failover of a cluster using vSphere HA and VMware vSphere Distributed Resource Scheduler (vSphere DRS)

    A virtual machine might power on slowly with a delay of 5 minutes, after a failover of a cluster that is set up with vSphere HA, vSphere DRS, and a View Connection Server using the power policy Ensure machines are always powered on.

    This issue is resolved in this release. 

  • The vpxd service fails with an error vpxd!FdmManager::WaitForUpdatesDone Panic: Win32 exception: Access Violation (0xc0000005)

    Specific race conditions or network partitions in a VMware High Availability cluster might cause the election of a master node to fail. As a result, when an update runs on a vCenter Server system and no master node is available, the vpxd service fails with an error vpxd!FdmManager::WaitForUpdatesDone Panic: Win32 exception: Access Violation (0xc0000005).

    This issue is resolved in this release. Restarting vpxd is a workaround in such scenarios but does not prevent subsequent failures. This fix removes the root cause of the issue.

Virtual Machine Management Issues
  • Orphaned snapshot entries in the VPX_TEXT_ARRAY table might increase the size of the vCenter Server database

    When you create a snapshot of a virtual machine, multiple entries might be added to the VPX_TEXT_ARRAY table of the vCenter Server database. Deleting the snapshot might fail to remove these entries causing the increase of the database size. As a result, the vCenter Server system might slow down and stop responding.

    This issue is resolved in this release.

  • vSphere Web Client might not show correct storage allocation after an increase of the disk size of a virtual machine

    If you use vSphere Web Client to increase the disk size of a virtual machine, the UI might not fully reflect the reconfiguration and show the storage allocation of the virtual machine unchanged.

    This issue is resolved in this release.

  • When you reconfigure VMware vSphere vApp (vApp) properties of a virtual machine, one or more virtual machines might fail to power on

    When you reconfigure vApp properties of a virtual machine, one or more virtual machines might fail to power on if the previous reconfigure operation has failed with a Concurrent Access or InvalidIndexArgument exception. The vApp config state in the vCenter Server system already contains the changes from the previous call and the current call fails with an exception because it tries to add a configuration that appears as existing.

    This issue is resolved in this release.

Networking Issues
  • The vpxd service might run out of memory in large deployments with complex traffic filters if a transaction element in an API call is not deleted

    In large deployments with complex traffic filters configured on distributed virtual port groups, if a transaction element in an API call is not deleted, the vpxd service might run out of memory and fail. When the call invokeHostTransactionCall to vpxa times out or gets interrupted, the transaction element in _transactionMap might not be removed and causes a memory leak.

    This issue is resolved in this release. 

  • 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.

Guest OS Issues
  • You might not see a taskbar if you open a virtual machine console by using either the vSphere Client or vSphere Web Client

    You might not see a taskbar if you open a virtual machine console by using either the vSphere Client or vSphere Web Client unless in full screen mode. Changing display resolutions does not solve the issue. However, you can see the taskbar if you navigate to the ESXi host in the vCenter Server system by using either the vSphere Client or vSphere Web Client.

    This issue is resolved in this release.

Storage Issues
  • The vSphere Web Client cannot display files in a datastore due to a timeout

    When a single folder in a datastore contains more than 2400 vmdk files, browsing that folder by using the vSphere Web Client might timeout. You might see an error message similar to The query execution timed out because of a back-end property provider 'com.vmware.vsphere.client.storage.impl.FilePropertyProvider' which took more than 120 seconds. The timeout is due to the ineffective search process. Before the fix, the search process for the vmdk files scanned all the disk files, including both the descriptor and flat.vmdk files. Since flat.vmdk files might be large and all their information is stored in the descriptor files, the current search skips scanning the flat.vmdk files.

    This issue is resolved in this release.

  • vSphere Storage DRS load balancing of multiple thin provisioned disks might take long and block other processes

    If you create multiple thin provisioned disks on a datastore, vSphere Storage DRS might run into an infinite loop while trying to balance loads. As a result, the load balancing operation might block other vSphere Storage DRS processes and affect the performance.

    This issue is resolved in this release.

vSAN Issues
  • Unable to start vSAN health service because health configuration file is empty

    The vSAN health configuration file might become corrupted, due to no disk quota or if the thread is killed. When this problem occurs while setting vSAN health configuration, the health service cannot start.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Auto Deploy Issues
  • TLS reconfiguration fails after a minor update of vCenter Server for Windows

    TLS reconfiguration fails after a minor update of vCenter Server for Windows, for instance from vCenter Server 6.0 Update 3b to vCenter Server 6.0 Update 3i, while enabling TLSv1.2.

    Workaround: Manually start the Auto Deploy service and configure the entire vCenter Server system with the command reconfigureVc update -p TLSv1.2.

Known Issues from Earlier Releases

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