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

vCenter Server 6.7 Update 3a |  OCT 24 2019 | ISO Build 14836122

vCenter Server Appliance 6.7 Update 3a | OCT 24 2019 | ISO Build 14836122

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

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

Earlier Releases of vCenter Server 6.7

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.7 are:

For internationalization, compatibility, installation and upgrade, open source components and product support notices see the VMware vCenter Sever 6.7 Update 3 Release Notes.

Patches Contained in This Release

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

Full Patch for VMware vCenter Server Appliance 6.7 Update 3a

Product Patch for vCenter Server Appliance 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.7.0.41000-14836122-patch-FP.iso
Build 14836122
Download Size 1980.5 MB
md5sum 1e40d29f27ba5f5c901425ce781e7baf
sha1checksum c50191f9eda460b39f44c03a4a8a725d611320f3

Download and Installation

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

  1. Attach the VMware-vCenter-Server-Appliance-6.7.0.41000-14836122-patch-FP.iso file to the vCenter Server Appliance CD or DVD drive.
  2. Log in to the appliance shell with your root credentials 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 using the vCenter Server Appliance shells, see VMware knowledge base article 2100508.

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.

Resolved Issues

The resolved issues are grouped as follows.

Security
  • You cannot enforce strict certificate validation for file-based backup and restore operations

    With vCenter Server 6.7 Update 3a, you can enforce strict certificate validation for file-based backup and restore operations by including the root CA certificate in all file transfers.

    This issue is resolved in this release. For more information, see VMware knowledge base article 75156.

Convergence Issues
  • Convergence of a vCenter Server instance with an external Platform Services Controller to a vCenter Server instance with an embedded Platform Services Controller fails with error 41204

    Due to a rare race condition, convergence of a vCenter Server instance with an external Platform Services Controller to a vCenter Server instance with an embedded Platform Services Controller might fail. You see an error similar to:
    2019-07-18T10:46:06.679Z Running command: ['/opt/likewise/bin/lwsm', 'status', 'vmdns']
    2019-07-18T10:46:06.687Z Error: LW_ERROR_NO_SUCH_SERVICE (41204)
    No service with the specified name exists

    This issue is resolved in this release.

  • Convergence, domain repointing and fresh installation of a vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode might fail with error install.vmafd.vmdir_vdcpromo_error_21 

    The following operations might fail with an error similar to: id: install.vmafd.vmdir_vdcpromo_error_21 in the /var/log/firstboot/vmafd-firstboot.py_ _stderr.log file:

    • Converging instances of vCenter Server Appliance with an external Platform Services Controller instances into vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode.  
    • Repointing a vCenter Server with an Embedded Platform Services Controller to a new domain.  
    • Adding a new vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode.

    This issue is resolved in this release.

vSAN Issues
  • vSAN UI does not appear in vSphere Client after upgrade to 6.7 Update 3

    If your vCenter Server system was originally at version 5.5 or earlier, the server UUID is in uppercase. When you upgrade to 6.7 Update 3, this causes a problem that blocks the vSAN UI from appearing in the vSphere Client.
    You might see a similar message in the vSphere HTML UI log file:
    Caused by: com.vmware.vsphere.client.vsandp.core.sessionmanager.common.NotAuthenticatedException:
    Authentication information for the specified site is missing. Authenticate with the site and try again.
    at com.vmware.vsphere.client.vsandp.core.sessionmanager.common.VcClient.getConnection
    Caused by: com.vmware.vsphere.client.vsandp.core.sessionmanager.vlsi.client.sso.tokenstore.NoTokenException: No token for site: 3D428B1A-E589-47EB-BB83-B7D8A32A97E8

    A related issue occurs because vSAN used a legacy endpoint to connect to the vCenter Single Sign-On administration service, which causes the following error to appear: Certificate chain not trusted.

    These issues are resolved in this release.

Known Issues from Prior Releases

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