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

VMware vCenter Server 6.7 Update 1 Release Notes

vCenter Server 6.7 Update 1 | 16 OCT 2018 | ISO Build 10244745

vCenter Server Appliance 6.7 Update 1 | 16 OCT 2018 | Build 10244745

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

  • With vCenter Server 6.7 Update 1, you can move a vCenter Server with an Embedded Platform Services Controller from one vSphere domain to another vSphere domain. Services such as tagging and licensing are retained and migrated to the new domain. For more information, see the vCenter Server Installation and Setup Guide.
  • vCenter Server 6.7 Update 1 adds screening for issues in your vSphere environment that proactively provides links to relevant VMware knowledge base articles. For more information, see Check vSphere Health in vSphere Client.
  • vCenter Server 6.7 Update 1 adds support for virtual machine (.vmtx) templates in the Content Library Service.
  • vCenter Server 6.7 Update 1 adds a CLI tool to convert 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.
  • Burst Filter: vCenter Server 6.7 Update 1 adds a Burst Filter to manage event bursts and prevent the database of vCenter Server from flooding with identical events over a short period of time.
  • vCenter Server 6.7 Update 1 supports VMware vSphere vMotion between on-prem systems and VMware Cloud on AWS. You can use either the vSphere Client or vSphere Web Client, or the API. To enable the feature, you must upgrade the source on-prem vCenter Server system to vCenter Server 6.7 Update 1 and ESXi 6.7 Update 1.
  • With vCenter Server 6.7 Update 1, you can import Open Virtual Appliance (OVA) files in a Content Library. The OVA files are unzipped during the import, providing manifest and certificate validations, and create an OVF library item that enables deployment of virtual machines from a Content Library.
  • With vCenter Server 6.7 Update 1, you can restore external Platform Services Controller instances which are replicating data with other external Platform Services Controller instances. This includes restore of external Platform Services Controller instances in all topologies supported in replication mode. The external Platform Services Controller being restored syncs with active peers or if no replication partner is available, it is restored to a backed-up state.
  • Create and Extend Hyper-Converged Infrastructure (HCI): The Create/Extend HCI cluster feature provides a guided user experience for configuration of vSphere and vSAN clusters. The feature also delivers a centralized wizard experience, embeds best practice, and automates repetitive operations.
  • With vCenter Server 6.7 Update 1, you can use the Appliance Management User Interface to configure and edit the firewall settings of the vCenter Server Appliance.
  • With vCenter Server 6.7 Update 1, users with vCenter Single Sign-On administrator privileges, who are part of the SystemConfiguration.BashShellAdministrator group, can access and manage the vCenter Server Appliance by using the Bash shell.
  • vCenter Server 6.7 Update 1 supports Windows 2016 Active Directory.
  • vCenter Server 6.7 Update 1 adds support for configuration and monitoring of vCenter High Availability by using the vSphere Client.
  • With vCenter Server 6.7 Update 1, you can change color schemes in the vSphere Client to display the interface in a dark theme.
  • AppDefense vCenter Server Plugin: vCenter Server 6.7 Update 1 introduces VMware Appdefense as an integrated component of vCenter Server. The AppDefense vCenter Server Plugin provides aggregated security metrics, visibility, and health statistics for applications and workloads running on vSphere.
  • AppDefense lifecycle management: vCenter Server 6.7 Update 1 supports one-click, integrated installation and upgrade workflows for AppDefense directly within vCenter Server. For more information, see the AppDefense Installation Guide with vCenter Server Plugin.
  • AppDefense virtual machine monitoring: vCenter Server 6.7 Update 1 supports AppDefense behavior monitoring for visibility, security assessment, and troubleshooting directly within vCenter Server. For more information, see the AppDefense User Guide.

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 open source components, list of disallowed or unsupported CPUs, and product support notices see the VMware vSphere 6.7 Release Notes.

Patches Contained in This Release

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

Security Patch for VMware vCenter Server 6.7 Update 1

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

For vCenter Server and Platform Services Controller for Windows

Download Filename VMware-VIMPatch-T-6.7.0-10244745.iso
Build 10244745
Download Size 40.8 MB
md5sum 019d4ff13fb3fecdab5ae012abb081f7
sha1checksum aaf8ab3c267ef9ea261fd00208e8cb2c882feac5

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 by Product drop-down menu. 

  1. Mount the VMware-VIMPatch-T-6.7.0-10244745.iso file 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.7 Update 1

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.20000-10244745-patch-FP.iso
Build 10244745
Download Size 1929.4 MB
md5sum 5e537ca6cea4e4931ba569b30cbac78c
sha1checksum f063c224f54b54e757d599473818c3c52a6ecf18

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.7.0.20000-10244745-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.

Internationalization

VMware vSphere 6.7 Update 1 is available in the following languages:

  • English
  • French
  • German
  • Spanish
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Components of vSphere 6.7 Update 1, including vCenter Server, vCenter Server Appliance, ESXi, the vSphere Client, the vSphere Web Client, and the VMware Host Client, do not accept non-ASCII input.

Compatibility

ESXi and vCenter Server Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.

vSphere Update Manager, vSphere Client, and vSphere Web Client are packaged with vCenter Server.

Hardware Compatibility for ESXi

To view a list of processors, storage devices, SAN arrays, and I/O devices that are compatible with vSphere 6.7 Update 1, use the ESXi 6.7 Update 1 information in the VMware Compatibility Guide.

Device Compatibility for ESXi

To determine which devices are compatible with ESXi 6.7 Update 1, use the ESXi 6.7 Update 1 information in the VMware Compatibility Guide.

Guest Operating System Compatibility for ESXi

To determine which guest operating systems are compatible with vSphere 6.7 Update 1, use the ESXi 6.7 Update 1 information in the VMware Compatibility Guide.

Virtual Machine Compatibility for ESXi

Virtual machines that are compatible with ESX 3.x and later (hardware version 4) are supported with ESXi 6.7 Update 1. Virtual machines that are compatible with ESX 2.x and later (hardware version 3) are not supported. To use such virtual machines on ESXi 6.7 Update 1, upgrade the virtual machine compatibility. See the ESXi Upgrade documentation.

Installation and Upgrade Notes for This Release

Installation Notes for This Release

Read the ESXi Installation and Setup and the vCenter Server Installation and Setup documentation for guidance about installing and configuring ESXi and vCenter Server.

Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:

VMware introduces a new Configuration Maximums tool to help you plan your vSphere deployments. Use this tool to view VMware-recommended limits for virtual machines, ESXi, vCenter Server, vSAN, networking, and so on. You can also compare limits for two or more product releases. The VMware Configuration Maximums tool is best viewed on larger format devices such as desktops and laptops.

Migrating Third-Party Solutions

For information about upgrading with third-party customizations, see the ESXi Upgrade documentation. For information about using Image Builder to make a custom ISO, see the ESXi Installation and Setup documentation.

Upgrade Notes for This Release

IMPORTANT: Before an upgrade, always verify in the VMware Product Interoperability Matrix compatible upgrade paths from earlier versions of ESXi and vCenter Server to the current version. 

For instructions about upgrading ESXi hosts and vCenter Server, see the ESXi Upgrade and the vCenter Server Upgrade documentation.

Resolved Issues

The resolved issues are grouped as follows.

Miscellaneous Issues
  • Compliance checks might fail with an error for the UserVars.ESXiVPsDisabledProtocols option when an ESXi host upgraded to version 6.7 is attached to a host profile with version 6.0

    The issue might occur when you perform the following actions:

    1. Extract a host profile from an ESXi host with version 6.0.
    2. Upgrade the ESXi host to version 6.7.
    3. The host appears as non-compliant for the UserVars.ESXiVPsDisabledProtocols option even after remediation.

    This issue is resolved in this release.

  • The vpxd service might fail intermittently due to a thread race

    The vpxd service might fail intermittently due to a thread race in the propertyCollector service. During a system update, overlapping blocking calls might lead to the use of a filter that is no longer existing and cause the vpxd failure.

    This issue is resolved in this release.

  • Unable to unstage patches when using an external Platform Services Controller

    If you are patching an external Platform Services Controller (an MxN topology) by using the VMWare Appliance Management Interface, with patches staged to an update repository, and then attempt to unstage the patches, you might see the following error message:

    Error in method invocation [Errno 2] No such file or directory: '/storage/core/software-update/stage' 

    This issue is resolved in this release.

  • The set sorting order for column values in the Performance Chart Legend grid is not retained after a data refresh

    In the advanced performance charts of the vSphere Web Client, when you set an ascending or descending order for the column values in the Performance Chart Legend grid, the order might be disrupted on data refresh. 

    This issue is resolved in this release.

  • The vSphere Certificate Manager utility fails to replace a machine SSL certificate if it contains extra details in the Subject Alternative Name (SAN) field

    The vSphere Certificate Manager utility might fail to replace a machine SSL certificate if you specify additional details in the SAN field, such as sites, IP addresses, and common names.

    This issue is resolved in this release. With this fix, the vSphere Certificate Manager only checks the system name in the SAN field of machine SSL certificates.

  • vCenter Server might stop responding if an ESXi host is removed from the inventory

    vCenter Server might stop responding if an ESXi host is removed from the inventory at the time the vCenter Server system starts up.

    This issue is resolved in this release.

  • You cannot configure the remote log server domain name to start with a digit

    If you configure the domain name of a remote log server for vCenter Server Appliance to start with a digit, for example syslog.9dc.com, the server might fail with syslog.invalid.configuration error.

    This issue is resolved in this release.

  • Disk usage of syslog files might grow exponentially due to an issue with the log rotation

    Log rotation and compression for some syslog files might stop after the first round and file size might grow significantly. The affected files are: /var/log/vmware/messages/var/log/vmware/*/*-syslog.log and /var/log/vmware/esx/*/*-syslog.log.

    This issue is resolved in this release.

Networking Issues
  • Link Aggregation Groups might be lost during the import of a vSphere Distributed Switch configuration

    If you import a vSphere Distributed Switch configuration with many Link Aggregation Groups (LAGs), the vCenter Server daemon service vpxd might fail to insert the corresponding LAG information to the vCenter Server database, and some LAGs might be missing after a restart of the vpxd service.

    This issue is resolved in this release. However, if you already face the issue, delete and reimport the vSphere Distributed Switch configuration, or create the missing LAG manually. 

  • Deploying a virtual machine from a template with a static MAC address or cloning a template to another template with a static MAC address might trigger an alarm

    Deploying a virtual machine from a template with a static MAC address or cloning a template to another template with a static MAC address might trigger a VM Static MAC Conflict alarm. Although the virtual machine template is not an active virtual machine, the vCenter Server system runs a VM MAC conflict check on the template.

    This issue is resolved in this release. 

  • You might see VLAN health check alarms for NSX logical switch port groups and ports connected to such port groups in a vSphere Distributed Switch

    If you enable the health check service on a VLAN in a VDS, which contains NSX logical switch port groups, you might see a health check alarm. This fix prevents incorrect health check alarms for the VLAN settings of NSX logical switch port groups.

    This issue is resolved in this release.

  • Performance of a VXLAN environment might degrade if IPFIX has a high sampling rate and traffic is heavy

    When you enable IPFIX with a high sampling rate and traffic is heavy, you might see degraded performance of a VXLAN environment.

    This issue is resolved in this release. Use lower sampling rates to optimize performance.

  • Тhe vCenter Server Appliance Management Interface might display an error message without the necessary details, because user input prompts are incorrect

    When you configure proxy settings by using the Appliance Management Interface, and you specify just an IP address or FQDN as prompted, you might see an error HTTP Error in method invocation list index out of range. The actual format required for the proxy settings is not an IP address or FQDN, but follows the pattern http://FQDN_or_IP or https://FQDN_or_IP.

    This issue is resolved in this release. This fix improves the user interface label and adds a prompt to provide a supported protocol in the proxy server URL field.

Security Issues
  • Update to vPostgres

    vPostgres is updated to 9.6.9.

  • Update to Procmail

    Procmail is updated to 3.22-4.

  • Update to cURL

    cURL in the vCenter Server Appliance is updated to 7.59.0.

  • Upgrade of Eclipse Jetty

    Eclipse Jetty is upgraded to version 9.2.24.

  • Document Type Definition issue in the Apache Xerces-C++ library

    Due to a security issue discovered in the Xerces-C++ library with identifier CVE-2017-12627, the XML validation using the --schemaValidate flag is disabled in the VMware OVF Tool.

    This issue is resolved in this release.

  • Update to OpenSSL library

    The OpenSSL library is updated to version openssl-1.0.2o.

  • Update of the SQLite database

    The SQLite database is updated to version 3.22.

  • Update to the libPNG library

    The libPNG library is updated to libpng-1.6.34.

  • Update to the Python library

    The Python third party library is updated to version 3.5.5 to resolve issues with identifiers CVE-2014-3539, CVE-2017-1000158, CVE-2016-5636 and CVE-2017-17522.

  • Update to the Apache Tomcat server

    The Apache Tomcat server is updated to version 8.5.32.

  • Update to the libxml library

    The vCenter Server service vmware-vpxd libxml2 library is updated to version 2.9.8.

  • Update to Ehcache

    The Ehcache package is updated to version 3.4.0.

  • Update to JRE package

    The Oracle (Sun) JRE package is updated to version 1.8.0.181.

  • Update to Apache Struts

    Apache Struts is updated to version 2.5.17 to resolve CVE-2018-1327 and CVE-2018-11776.

  • Update to glibc package

    The glibc package is updated to version 2.22-21.

Storage Issues
  • Unregistering a VMware vSphere API for Storage Awareness provider in a disconnected state might result in an error

    If you unregister a vSphere API for Storage Awareness provider in a disconnected state, you might see a java.lang.NullPointerException error. Event and alarm managers are not initialized when a provider is in a disconnected state, which causes the error.

    This issue is resolved in this release.

  • Upload or download of ISO files from a datastore might fail due to insufficient privileges

    Upload or download of ISO files from a datastore might require Datastore.FileManagement privileges on datastore level and if such privileges are not assigned, upload or download of ISO files from the datastore might fail. In the vSphere Client, you might see the error Unauthorized. This fix removes the requirement for Datastore.FileManagement privileges for file upload and download.

    This issue is resolved in this release.

Installation Issues
  • Update to the lxml open-source package in vCenter Server Appliance CLI installer

    The lxml open-source package in vCenter Server Appliance CLI installer is updated to version 4.2.1.37.

  • External deployment of a second Platform Services Controller in an existing vCenter Single Sign-On domain might fail

    External deployment of a second Platform Services Controller in an existing vCenter Single Sign-On domain might fail in stage 2 with the error: 

    Unable to validate the connectivity to the external Platform Services Controller. Failed to validate sso.

    This issue is resolved in this release.

  • The GUI installer might display one and the same error message caused by firstboot failures during upgrade or installation of a vCenter Server Appliance

    The GUI installer might display one and the same error message caused by firstboot failures during vCenter Server Appliance installation or upgrade. The message is:

    /etc/systemd/system/vmware-vmon.service.d/dep_override.conf.tmp.

    This issue is resolved in this release. Firstboot failures generate error-specific messages.

Upgrade Issues
  • Upgrade of the vCenter Server Appliance which uses DNS servers with enabled DNS Security Extensions (DNSSEC) might fail

    The upgrade of the vCenter Server Appliance which uses DNS servers with enabled DNSSEC might fail. This issue occurs because while resolving the host name, the vCenter Server system might pick the resource record digital signature (RRSIG) of the DNSSEC instead of the IP address.

    This issue is resolved in this release.

  • Upgrade to vCenter Server 6.7 might fail with an error that an IP already exists

    In stage 2 of the upgrade of the vCenter Server Appliance, the source appliance must be shut down. If the shutdown of the source appliance takes a long time, the upgrade might fail. This is because the network of the source appliance is  still active, and the newly deployed target appliance cannot apply network settings.

    You might see an error IP already exists in the network.

    This issue is resolved in this release.

Virtual Machines Management Issues
  • Deleting the NSX Guest Introspection service for a cluster might fail with an error

    If vSphere ESX Agent Manager raises vmIssue and does not provide the Managed Object Reference ID of the virtual machine, the API requests to the vSphere ESX Agent Manager server might fail due to serialization and deserialization problems. You might see a message Error occurred while communicating with ESXi Agent Manager.

    This issue is resolved in this release.

  • Deploying a new VMware vSphere Replication appliance 6.5.1 in a cluster without a shared storage might fail with an error

    When you try to deploy a VMware vSphere Replication appliance 6.5.1 in a cluster without a shared storage, the OvfManager.createImportSpec() API call might fail. As a result, the deployment might fail with the following error:

    The given OVF descriptor is invalid.

    This issue is resolved in this release.

  • Deployment of a virtual machine from a custom OVF file might fail

    Deployment of a virtual machine from a custom OVF file might fail if no attribute namespace prefix is specified, and the system uses the default namespace. You might see an error ATTRIBUTE_REQUIRED.

    This issue is resolved in this release.

  • Cross-vCenter Server migration of a virtual machine to a cluster by using vSphere vMotion might fail on vCenter Server 6.7

    Cross-vCenter Server migration of a virtual machine to a cluster by using vSphere vMotion might fail on vCenter Server 6.7. vSphere Storage DRS displays this error:
    com.vmware.sdrs.disk.dsunspecified.

    This issue is resolved in this release.

  • Undeleted tasks in a vCenter Server system might fail Content Library service tasks

    When the Content Library service starts up, it cleans outstanding tasks from its database. Sometimes, outstanding tasks in a vCenter Server system are not properly indicated and pile as unresolved, which might lead to failure of new tasks.

    This issue is resolved in this release.

  • The Content Library service might create a library backed by an SMB share even if the SMB mount fails, and the library consumes storage space from the vCenter Server system

    If you create a content library backed by an SMB share in a vCenterServer Appliance, but the SMB mount fails, any uploaded content in the library still takes storage space from the vCenter Server system. The issue does not affect NFS mounts.

    This issue is resolved in this release. If you already face the issue, see VMware knowledge base articles 58932 and 57867.

Tools Issues
  • The OVF Tool might fail to read an ISO file when it is attached to an OVA file

    When you deploy an OVA template with an attached ISO file to vCenter Server or directly to an ESXi host, the OVF Tool might not read the ISO file and the deployment might fail with the following error: File Not Found.   

    This issue is resolved in this release.

  • Import of a virtual machine with a VMware Paravirtual SCSI disk adapter type might fail

    When you use VMware Workstation or VMware Fusion to import a virtual machine with a VMware Paravirtual SCSI (PVSCSI) disk adapter type, the import operation might fail with the following error: 

    Invalid target disk adapter type: pvscsi.

    This issue is resolved in this release.

  • Importing or exporting virtual machines with sound card adapters might fail

    In VMware Workstation and VMware Fusion, importing or exporting virtual machines with sound card adapters might fail with

    Unknown error, please try again.

    This issue is resolved in this release.

  • You might fail to deploy virtual machines on VMware vCloud Director by using the OVF Tool due to outdated API versions

    You might fail to deploy virtual machines on vCloud Director by using the OVF Tool, because it supports obsolete vCloud Director API versions.

    This issue is resolved in this release.

  • IPv6 loopback entries might be deleted during Linux customizations

    During Linux customizations, IPv6 loopback entries might be accidentally deleted from the /etc/hosts file.

    This issue is resolved in this release.

Guest OS Issues
  • When you do a test recovery with IP customization of a virtual machine with Red Hat Enterprise Linux (RHEL) 7.x OS, the /etc/hostname file on the recovered instance might be empty

    When you do a test recovery with IP customization of a virtual machine with RHEL 7.x OS, the /etc/hostname file on the recovered instance might be empty. You might also see no double quotes for the DOMAIN key / value in the network file under/etc/sysconfig/network-scripts/.

    This issue is resolved in this release. If you already face the issue, use CLI to populate the hostname in the /etc/hostname file and to put the DOMAIN key/value in double quotes in the network file under /etc/sysconfig/network-scripts/.

Licensing Issues
  • ESXi hosts with custom certificates might automatically get a VMware Certificate Authority certificate

    ESXi hosts that use custom certificates might automatically get VMware CA certificates if the parameters vpxd.certmgmt.certs.hardThreshold and vpxd.certmgmt.certs.softThreshold of the vpxd.certmgmt.mode advanced option hit their limits.

    This issue is resolved in this release. 

  • Witness virtual machine consumes host license capacity from vCenter Server Essentials Plus

    A vSAN 2-host cluster (ROBO) requires two physical hosts and one witness. When the witness is an appliance that resides in a virtual machine, it incorrectly consumes a host license. This problem occurs because the vCenter Server considers the witness appliance to be a host. 

    Тhis issue is resolved in this release.

Internationalization Issues
  • Content Library content might fail to sync if file names in the source library contain non-ASCII characters

    Synchronization of Content Library content might fail in case a name of an item in the source library contains multibyte non-ASCII characters such as Chinese or Japanese.

    This issue is resolved in this release.

Server Configuration Issues
  • You cannot add or create an Active Directory over an LDAP identity source if SSL protection is active

    If you set up SSL protection by using the option Connect to any domain controller, in the vSphere Web Client you might see an error, A vCenter Single Sign-On service error occurred when trying to add or create an Active Directory over an LDAP identity source.

    This issue is resolved in this release. If you already face the issue, use the Specific domain controllers option to provide a URL that points to an actual domain controller as the primary server URL. Provide the SSL server certificate of this domain controller, making sure the certificate has the same subject name as the URL of the domain controller. 

CIM and API Issues
  • Invoking the methods checkMigrate, checkRelocate and checkClone with a hostTests test type might not run network related checks

    Invoking the methods checkMigrate, checkRelocate and checkClone with a hostTests test type might not run network related checks. Invoke the methods with a networkTests test type to run network related checks on selected destination host or cluster.

    This issue is resolved in this release.

  • SNMP does not list Java proces names correctly in hrSWRunPath queries

    If you run a hrSWRunPath query to identify the location of the long-term storage from which some software was loaded, the output might be incorrect, similar to: HOST-RESOURCES-MIB::hrSWRunPath.8260 = STRING: "/opt/vmware/bin/jsvc", because the query fetches data from /proc//smaps .    

    This issue is resolved in this release.

vSAN Issues
  • The Cluster Compliance status of a vSAN enabled cluster might display as Not compliant

    The Cluster Compliance status of a vSAN enabled cluster might display as Not compliant, because the compliance check might not recognize vSAN datastores as shared datastores.

    This issue is resolved in this release.

  • Error message about vSAN capacity appears after vSAN is disabled on a cluster

    When all disk groups are removed from a vSAN cluster, the vSphere Client displays a warning similar to the following: VMware vSAN cluster in datacenter does not have capacity. After you disable vSAN on the cluster, the warning message persists.

    This issue is resolved in this release.

  • Null pointer returned when executing Ruby vSphere Console (RVC) command vsan.whatif_host_failures

    If the properties of an ESXi host cannot be retrieved, a null pointer might be returned when you run the following RVC command: vsan.whatif_host_failures.

    This issue is resolved in this release.

  • vSAN capacity monitor shows lower Used Capacity than actual capacity used

    After you upgrade vCenter Server to 6.5 Update 2, the vSAN capacity monitor (Monitor > vSAN > Capacity) does not include capacity used by virtual machines on hosts running 6.5 Update 1 or older. The Used Capacity displayed is lower than the actual capacity used.

    This issue is resolved in this release.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • VMware vSphere Authentication Proxy configuration options are not visible in either the vSphere Web Client and the vSphere Client

    You might not see the Manage tab under System Configuration > Services > VMware vSphere Authentication Proxy in either the vSphere Web Client and the vSphere Client.

    This issue is resolved in this release.

  • When typing in the web-based WebMKS console of the vSphere Web Client in Mozilla Firefox, some characters might repeat

    When typing in the web-based WebMKS console of the vSphere Web Client in Mozilla Firefox, versions 54.0 or later, some characters might repeat.

    This issue is fixed in this release.

  • The Edit Host Customizations workflow in the vSphere Client might not keep customized values

    When you customize the settings of an ESXi host by changing values such as IP and netmask, the Edit Host Customizations workflow in the vSphere Client might not keep the customized values.The workflow works as expected in the vSphere Web Client.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Virtual Machines Management Issues
  • The Virtual Appliance Management Interface might display a 0- message or a blank page during patching from vCenter Server 6.7 to later versions

    The Virtual Appliance Management Interface might display a 0- message or a blank page during patching from vCenter Server 6.7 to later versions, if calls from the interface fail to reach the back end applmgmt service. You might also see the message Unable to get historical data import status. Check Server Status.

    Workaround: These are not failure messages. Refresh the browser and log in to the Virtual Appliance Management Interface again once the reboot of appliance in the back end is complete.

  • The Ready to Complete page of the Register Virtual Machine wizard displays only one horizontal line

    The Ready to Complete page of the Register Virtual Machine wizard might display content similar to one horizontal line due to a rendering issue. This issue does not affect the workflow of the wizard.

    Workaround: None

Installation, Upgrade and Migration Issues
  • Upgrading vCenter Server 6.5 for Windows to vCenter Server 6.7 might fail if the vSphere Authentication Proxy service is active

    If the vSphere Authentication Proxy service is active while you perform an upgrade from vCenter Server 6.5 for Windows to vCenter Server 6.7, the operation might fail during the pre-check. You might see an error similar to:

    The following non-configurable port(s) are already in use:
    2016, 7475, 7476
    Stop the process(es) that use these port(s)
    .

    Workaround: Stop the vSphere Authentication Proxy service. You can restart the service after the successful upgrade to vCenter Server 6.7.

  • Patching to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7 might fail when vCenter Server High Availability is active

    Patching to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7 might fail when vCenter Server High Availability is active due to a DB schema change. For more information, see VMware knowledge base article 55938.

    Workaround: To patch your system to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7, you must remove vCenter Server High Availability and delete passive and witness nodes. After the upgrade, you must re-create your vCenter Server High Availability clusters.

  • Upgrade to vCenter Server Appliance 6.7 Update 1 from vCenter Server Appliance 6.5 Update 2 and later, using custom HTTP and HTTPS ports, might fail

    Upgrades from vCenter Server Appliance 6.5 Update 2 and later, using custom HTTP and HTTPS ports, to vCenter Server Appliance 6.7 Update 1 might fail. You might see the issue regardless if you use the GUI or CLI installer.

    Workaround: None

  • Converging an external Platform Services Controller to a vCenter Server might fail if the Platform Services Controller uses a custom HTTPS port

    You might fail to converge an external Platform Services Controller to a vCenter Server system, if the vCenter Server system is configured with the default HTTPS port, 443, and the Platform Services Controller node is configured with a custom value for the HTTPS port. The operation fails in the firstboot stage due to convergence issues.

    Workaround: Change the HTTPS port value to the default value, 443, for vCenter Server nodes before running vCenter External to Embedded Convergence tool. You can run the following commands to do the same:

    1. /usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-port --server-name localhost --dc-port 443
    2. /usr/lib/vmware-vmafd/bin/vmafd-cli set-rhttpproxy-port --server-name localhost --rhttpproxy-port 443
CLI Issues
  • Views might switch from the appliance shell to the Direct Console User Interface during an upgrade of the vCenter Server Appliance by using the CLI installer

    During an upgrade of the vCenter Server Appliance by using the CLI installer, views might switch intermittently from the appliance shell to the Direct Console User Interface. Restarts of the applmgmt service during updates causes the issue.

    Workaround: Switch to appliance shell tty to monitor the progress. 

Miscellaneous Issues
  • Importing a .csv file overwrites user input during host customization.

    User input in the Customize hosts pane is overwritten by the import process and the values from the .csv file.

    Workaround: Import the .csv file before adding manual changes in the Customize hosts pane.

  • The vCenter Server Convergence Tool might fail to convert an external Platform Services Controller to an embedded Platform Services Controller due to conflicting IP and FQDN

    If you have configured an external Platform Services Controller with an IP address as an optional FQDN field during the deployment, the vCenter Server Convergence Tool might fail to convert the external Platform Services Controller to an embedded Platform Services Controller because of a name conflict.

    Workaround: Do not use the vCenter Server Convergence Tool for Platform Services Controllers installed with an IP address as an alternative or addition to the FQDN address.

  • If you repoint and reconfigure the setup of a Platform Services Controller, the restore process might fail

    If you repoint and reconfigure the setup of a Platform Services Controller, the restore process might fail due to a stale service ID entry.

    Workaround: Follow the steps in VMware knowledge base article 2131327 to clean up the stale service ID before proceeding with restore.

  • Attempts to log in to a vCenter Server system after an upgrade to vCenter Server 6.7 might fail with a credentials validation error

    After an upgrade of your system to vCenter Server 6.7, if you try to log in to the system by using either the vSphere Web Client or vSphere Client, and a security token or smartcard, the login might fail with an error Unable to validate the submitted credential.

    Workaround: Remove and re-add the identity source. For more information, see Add or Edit a vCenter Single Sign-On Identity Source

  • An Enhanced vMotion Compatibility (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.

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

  • Some vCenter Server plug-ins might not correctly render the dark theme mode in the vSphere Client

    If you change color schemes in the vSphere Client to display the interface in a dark theme, some vCenter Server plug-ins might not correctly render the mode.

    Workaround: None

  • If you enable per-VM EVC, virtual machines might fail to power on

    If you install or use for upgrade only VMware vCenter Server 6.7 Update 1, but do not apply ESXi 6.7 Update 1, and if you configure or reconfigure per-VM EVC, virtual machines on unpatched hosts might fail to power on. You might also see the issue if you enable cluster-level EVC and even one of the hosts in the cluster is not patched with the latest update. The new CPU IDs of that cluster might not be available on the cluster. In such a cluster, if you configure or reconfigure per-VM EVC, virtual machines might fail to power on.

    Workaround: Before you configure or reconfigure per-VM EVC, upgrade all the standalone ESXi hosts, as well as hosts inside a cluster, to the latest update for hypervisor-assisted guest mitigation for guest operating systems.

  • Edits to the DNS settings might cause deletion of the IPv6 loopback address from the /etc/resolv.conf and /etc/systemd/resolved.conf files

    Edits to the DNS settings by using either the Appliance Management Interface, appliance shell, or the vSphere Web Client, might cause deletion of the IPv6 loopback address from the/etc/resolv.conf and /etc/systemd/resolved.conf files.

    Workaround: To avoid deletion of the IPv6 loopback address, edit the resolv.conf files by using the Bash shell:

    1. In the /etc/resolv.conf file, set the following parameters:

      nameserver: ::1
      nameserver: <dnsserver 1>
      nameserver: <dnsserver 2>

    2. In the /etc/systemd/resolved.conf file, set the following parameters:

      [Resolve]
      LLMNR=false
      DNS=::1 <dnsserver 1> <dnsserver 2>

  • The SSH service might be disabled after an external Platform Services Controller converts to an embedded Platform Services Controller

    If you convert an external Platform Services Controller to an embedded Platform Services Controller, the SSH service might be disabled based on Active Directory policies and restrictions.

    Workaround: Manually enable the SSH service after the conversion is complete.

Internationalization Issues
  • A VMkernel network using an NSX logical switch might fail for stateless hosts if you register vCenter Server with non-ASCII characters on VMware NSX Manager

    If you register vCenter Server to an NSX Manager with a password containing characters from the extended ASCII codes between 128 and 255, or non-ASCII characters, a VMkernel network using an NSX logical switch might be lost after deploying a stateless host.

    Workaround: Register vCenter Server to an NSX Manager with a password containing only ASCII characters.

  • An ESXi host might stop responding if you add a vSphere Distributed Switch named with a string containing tens of non-ASCII characters to a physical adapter in a hyper-converged infrastructure (HCI) cluster

    If you name a VDS with a string containing more than 40 characters from the extended ASCII codes between 128 and 255, or more than 26 non-ASCII characters, ESXi hosts might stop responding when you attempt to add the VDS to a physical adapter during the configuration of a hyper-converged infrastructure (HCI) cluster.

    Workaround: Use strings with less than 40 characters from the extended ASCII codes and 26 non-ASCII characters when naming a VDS.

VMware High Availability and Fault Tolerance Issues
  • vCenter Server High Availability cluster configuration by using an NSX-T logical switch might fail

    Configuration of a vCenter Server High Availability cluster by using an NSX-T logical switch might fail with the error Failed to connect peer node.

    Workaround: Configure vCenter Server High Availability clusters by using a vSphere Distributed Switch.

  • You cannot add ESXi hosts running vSphere Fault Tolerance workloads to a vCenter Server system by using the vSphere Client

    Attempts to add ESXi hosts running vSphere Fault Tolerance workloads to a vCenter Server system by using the vSphere Client might fail with the error Cannot add a host with virtual machines that have Fault Tolerance turned on as a stand-alone host.

    Workaround: As alternatives, you can:

    1. Schedule a task to add the host and execute it immediately.
      1. In the vSphere Client, navigate to Configure > Scheduled tasks for a selected cluster.
      2. Select New scheduled task > Add Host.
      3. Schedule a time to run the task.
      4. Add a host and run the task.
      5. Delete the task after the host is added.
    2. Use the vSphere Web Client to add the host. Login to the vSphere Web Client and execute the standard add host workflow.
    3. Turn off the fault tolerance virtual machines temporarily, add the host to the new vCenter Server system, and then turn it on back again.
Tools Issues
  • The OVF Tool might fail to verify an SSL thumbprint if you use CLI

    If you set the SSL thumbprint value by using CLI, the OVF Tool might fail to verify the thumbprint. The issue is not monitored if you use the Direct Console User Interface (DCUI).

    Workaround: Use any of the following alternatives:

    • In the DCUI, specify the thumbprint in the section of ssl_certificate_verification.
    • In the DCUI, specify to ignore certificate thumbprint for ESXi by putting ssl_certificate_verification verification_mode to False.
    • Ignore all certificate thumbprints globally by using the command-line parameter: --no-ssl-certificate-verification.
    • Wait for the CLI prompt to accept the thumbprint that it receives from the source. 
vCenter Server, vSphere Web Client, and vSphere Client Issues
  • The vSphere Client and vSphere Web Client might not reflect update from vCenter Server 6.7 to vCenter Server 6.7 Update 1 for vCenter Server for Windows

    If you update vCenter Server for Windows from vCenter Server 6.7 to vCenter Server 6.7 Update 1, the build number details for vpxd in the Summary tab of both the vSphere Client and vSphere Web Client might not reflect the update and show version 6.7.0.

    Workaround: None.

Known Issues from Prior Releases

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