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

VMware vCenter Server 6.5 Update 2d Release Notes

vCenter Server 6.5 Update 2d | 29 NOV | 2018 | ISO Build 10964411
vCenter Server Appliance 6.5 Update 2d | 29 NOV 2018 | ISO Build 10964411

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

  • vCenter Server 6.5 Update 2d adds a CLI tool to convert instances of vCenter Server Appliance with an external Platform Services Controller into vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode. For more information, see the 6.7 vCenter Server Installation and Setup guide.
  • With vCenter Server 6.5 Update 2d, you can add VMware Platform Services Controller appliances to Active Directory 2016 domains.
  • With vCenter Server 6.5 Update 2d, you can use the new vRealize Operations Manager plug-in that provides specific metrics and high-level information about data centers, datastores, virtual machines, and ESXi hosts, to vCenter Server and vSAN. The plug-in is supported only in the vSphere Client.
  • With vCenter Server 6.5 Update 2d, the new vRealize Operations Manager plug-in adds by default the Patch method, supported by the HTTP protocol, to facilitate the online installation stage.
  • With vCenter Server 6.5 Update 2d, you can configure the property config.vpxd.macAllocScheme.method in the vCenter Server configuration file, vpxd.cfg, to allow sequential selection of MAC addresses from MAC address pools. The default option for random selection does not change. Modifying the MAC address allocation policy does not affect MAC addresses for existing virtual machines.
  • vCenter Server 6.5 Update 2d 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.

    For Update Manager functionality differences between the vSphere Web Client and vSphere Client, see the VMware vSphere Update Manager 6.5 Update 2d Release Notes.

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 compatibility, installation and upgrades, product support notices, and features see the VMware vCenter Server 6.5 Update 2 Release Notes.

Patches Contained in This Release

vCenter Server 6.5 Update 2d delivers the following patch. See the VMware Patch Download Center for more information on downloading patches.

Security Patch for VMware vCenter Server 6.5 Update 2d

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

For vCenter Server and Platform Services Controller for Windows

Download Filename VMware-VIMPatch-T-6.5.0-10964411.iso
Build 10964411
Download Size 41.0 MB
md5sum 0477c9432e2068c013b75eca68450d88
sha1checksum 1452ec814067b5599b6afeb61674200a97fa3384

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.5.0-10964411.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 2d

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.23000-10964411-patch-FP.iso
Build 10964411
Download Size 1667.7 MB
md5sum 0d38c67b7a9af0d1e7f038e4e95c8e8b
sha1checksum ee46c1b6a8c10e2ec11eb71f02388f6f456037e8

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.5.0.23000-10964411-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 Photon OS updates, see VMware vCenter Server Appliance Photon OS Security 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.5 Update 2d to vCenter Server 6.7 Update 1 are not supported.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • You cannot use the TLS Configuration utility to change TLS settings while logging in to the Virtual Appliance Management Interface

    With this fix, you can toggle TLS protocols, such as switching from TLSv1.2 to TLSv1, by using the TLS Configuration utility while logging in to the Virtual Appliance Management Interface.

    This issue is resolved in this release.

  • Update to the Spring Framework

    The Spring Framework is updated to 4.3.18.

  • Update to Ehcache

    The Ehcache version is updated to 3.4.0.

  • Update to the OpenSSH

    The OpenSSH version is updated to 7.4p1-7.

  • Update to vPostgres

    vPostgres is updated to 9.4.19.

  • Update to the NTP package

    The NTP package is updated to version 4.2.8p12.

  • Upgrade of Eclipse Jetty

    Eclipse Jetty is upgraded to version 9.2.26.v20180806.

  • Update to OpenSSL

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

  • Update to JRE

    Oracle (Sun) JRE is updated to version 1.8u192.

  • Apache server details, such as version, might appear on vCenter Server urls

    Apache server details, including the version, might appear on vCenter Server urls, such as https:// :9443/vsphere-client/inventory-viewer/locales/help . The Apache server details might be visible for all the context present in the product.  

    This issue is resolved in this release.

CIM and API Issues
  • The vCenter Server daemon vpxd service might fail due to a race condition

    The vCenter Server daemon vpxd service might fail due to a race condition if a script calls SessionManager.impersonateUser() and then SessionManager.Logout() before the call to SessionManager.impersonateUser() finishes. You might see a stack trace similar to:

    #8 0x000000e395247d45 in Vpxd::Session::CompleteSessionInit (authMgr=..., cnx=cnx@entry=0x7ff3dc794330, userName=...,
    authTypePassed=authTypePassed@entry=Vpxd::Session::UserAuthType::TokenAuth, token=..., locale=..., remoteIpAddress=..., hasFullAccess=false, alterSession=alterSession@entry=true, desiredOwnerKey=..., result=...) at bora/vpx/vpxd/auth/user.cpp:1496
    #9 0x000000e395248115 in ImpersonateToUser (result=..., locale=..., normalizedUserName=...) at bora/vpx/vpxd/auth/user.cpp:1238
    #10 Vpxd::Session::ImpersonateUser (userName=..., locale=..., result=...) at bora/vpx/vpxd/auth/user.cpp:1602
    #11 0x000000e39525a7ac in SessionManagerMo::ImpersonateUser (this=0x7ff43c195170, userName=..., locale=..., result=...) at bora/vpx/vpxd/auth/sessionManagerMo.cpp:1368

    This issue is resolved in this release.

  • SNMP does not list Java process 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, and similar to: HOST-RESOURCES-MIB::hrSWRunPath.8260 = STRING: "/opt/vmware/bin/jsvc".

    This issue is resolved in this release.

  • You might fail to call applmgmt APIs by using vCenter Single Sign-On user credentials after migrating from vCenter Server for Windows to vCenter Server Appliance

    You might fail to call applmgmt APIs by using vCenter Single Sign-On user credentials after migrating from vCenter Server for Windows to vCenter Server Appliance due to a background change in the hashing algorithm for the SAML token. For example, you might not be able to do backups by using VMware PowerCLI.

    This issue is resolved in this release.

  • BMC GUI might not display the ESXi host version

    The BMC GUI and the localcli plug-in in the ESXi console might not display the ESXi host version.

    This issue is resolved in this release.

  • SNMP monitoring systems might report incorrect memory statistics on ESXi hosts

    SNMP monitoring systems might report memory statistics on ESXi hosts different from the values that freetop or vmstat commands report. The issue occurs only if the number of CPUs is more than 9.

    This issue is resolved in this release. The fix aligns the formula that SNMP agents use with the other command-line tools.

  • The vmware-vmon service might time out before a spawned stop process completes its execution

    The vmware-vmon service might time out before stop commands spawned for its child processes and the the stop command process might remain running in the background. For instance, thepg_ctl stop -m fast command in PostgreSQL. As a result, an application might be forcibly closed or cause other issues.

    This issue is resolved in this release. The fix increases the timeout of the vmware-vmon service.

High Availability and Fault Tolerance Issues
  • Virtual machines might power on slowly after a failover of a cluster using vCenter Server High Availability 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 vCenter Server High Availability, vSphere DRS, and a View Connection Server using the power policy Ensure machines are always powered on.

    This issue is resolved in this release. 

vMotion Issues
  • vSphere vMotion operations for encrypted virtual machines might fail after a restart of the vCenter Sever system

    After a restart of a vCenter Server system, compatibility check errors might fail vSphere vMotion operations for encrypted virtual machines. You might see logs similar to:

    RuntimeFault.summary Session does not have Cryptographer.RegisterHost privilege.

    This issue is resolved in this release.

  • vSphere DRS might run migrations of virtual machines even when a cluster seems balanced

    In vSphere 6.5, 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 issue is resolved in this release.

  • The vCenter Server daemon vpxd service might fail with a signal type SIGABRT due to an empty string

    During a file-based backup, if the vpx.vmprov process refers an empty string, a signal type SIGABRT is triggered. This leads to a failure of the vpxd service.

    This issue is resolved in this release.

  • An ESXi host might become unresponsive when you use a VMkernel NIC in the vSphereProvisioning netstack for NFC traffic

    When you create and add a VMkernel NIC in the vSphereProvisioning netstack to use it for NFC traffic, the daemon handling the NFC connections might fail to clean up old connections. This might lead to an exhaustion of available processes. As a result, the host becomes unresponsive and unable to create new processes, including SSH processes needed to handle incoming connections. All subsequent operations fail.

    This issue is resolved in this release.

  • vCenter Server might stop responding during migration of virtual machines by using vSphere Storage vMotion or Cross vCenter Server vMotion

    When you try to perform Storage vMotion or Cross vCenter Server vMotion migration of a virtual machine with two or more snapshots that each contain the same independent disks, vCenter Server might become unresponsive.

    This issue is resolved in this release

  • Migration of virtual machines by using vSphere vMotion might fail after attempts to upgrade the virtual hardware to an existing version

    Migration of virtual machines by using vSphere vMotion might fail if you schedule an upgrade of the virtual hardware to an existing version, by using either the VMware Update Manager or API. You might see the error The destination host is not compatible with the hardware version to which the virtual machine is scheduled to be upgraded even when no hardware version upgrade is pending.

    This issue is resolved in this update.

  • The pre-build module service becomes unresponsive and some vCenter Server operations such as PreCloneCheckCallback time out

    In large environments, with more than 2,000 ESXi hosts, if you attempt operations such as clone or migrate virtual machines, or setup storage policies for a large number of hosts or virtual machines, the pre-build module service might become unresponsive. As a result, some vCenter Server operations such as PreCloneCheckCallback and PreMigrateCheckCallback might time out.

    This issue is resolved in this release.

Miscellaneous Issues
  • vCenter Server tasks might become unresponsive due to a deadlock

    vCenter Server tasks might become unresponsive due to a deadlock if a host level share lock follows a cluster level share lock.

    This issue is fixed 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.

  • The vpxd service might fail intermittently due to a thread race in the PropertyCollector object

    The vpxd service might fail intermittently due to a thread race in the PropertyCollector object. Overlapping blocking calls might lead to the use of an already destroyed filter in an update operation, which causes the vpxd failure.

    This issue is resolved in this release.

  • The vpxd service 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.

  • The vpxd service might fail if you log out immediately after initiating a FileManager task

    If you log out immediately after initiating a FileManager task such as delete, move or copy, vpxd might fail, because the task might not be picked up for execution from the task queue.

    This issue is resolved in this release.

  • The sendmail service fails to start after upgrading to vCenter Server Appliance 6.5.x

    When you upgrade to vCenter Server Appliance 6.5.x the sendmail.cf file is overwritten. As a result, the outgoing emails from the vCenter Server Appliance might be blocked. 

    This issue is resolved in this release.

  • Power-on or vSphere vMotion operations with virtual machines might fail with an infinite loop error

    Power-on or vSphere vMotion operations with virtual machines might fail with an infinite loop error if the .vmx configuration file is corrupt.

    This issue is resolved in this release.

  • vCenter Single Sign-On authentication might fail due to a memory leak in the VMware Identity Management Service

    A memory leak in the VMware Identity Management Service might cause a failure of the vCenter Single Sign-On authentication for users from LDAP domains.

    This issue is resolved in this release.

  • vCenter Server health status reports might intermittently become inaccessible due to authorization issues

    vCenter Server health status reports might intermittently become inaccessible due to authorization issues, even when using the administrator@vsphere.local credentials.

    This issue is resolved in this release.

  • You cannot log in to a vCenter Server system with RSA SecurID

    You might fail to log in to a vCenter Server system by using the vCenter Single Sign-On configuration tool and running the set_rsa_config command to configure the LDAP attribute with an external identity provider. The login attempt might fail, because the external identity provider match is case-sensitive. The UPN is used to validate the user account instead of the LDAP attribute and as a result, the RSA Agent logs the following error: PrincipalResolutionException: Unable to Resolve Principal: No aliases found, unable to resolve principal by alias.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • 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 vCenter Server 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.

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

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

    This issue is resolved in this release.

  • Editing a virtual machine might fail with TypeError: Error #1009

    When you log in to the vSphere Web Client and try to edit a virtual machine which has virtual disks attached to a storage profile, you might see TypeError: Error #1009.

    This issue is resolved in this release. 

  • Backup of virtual machines might fail with VDDK error 13 due to failing HTTP requests

    Backup of virtual machines might fail due to a failure of the datastore HTTP handler. You might see VDDK error message:
    Error 13 (You do not have access rights to this file).
    The error indicates that a datastore name contains non-alphanumeric characters and the HotAdd Transport Mode is set with the NoNfcSession parameter enabled, such as NoNfcSession=1.

    This issue is resolved in this release.

Installation, Upgrade, and Migration Issues
  • Migration of vCenter Server for Windows to vCenter Server Appliance might stop at 75% if the system time is not synchronized with an NTP server

    During stage 2 of the migration process from vCenter Server for Windows to vCenter Server Appliance, if the system time is not synchronized with an NTP server, the session might time out and the migration stops without a warning. The installer interface might indefinitely display progress at 75%.

    This issue is resolved in this release.

  • vCenter Server upgrades might fail due to compatibility issue between VMware Tools version 10.2 and later, and ESXi version 6.0 and earlier

    VMware Tools version 10.2 and later might not be compatible with ESXi version 6.0 and earlier. As a result, upgrades of vCenter Server systems might fail.

    This issue is resolved in this release. If you already face the issue, either update the ESXi host to a newer version or roll back the VMware Tools version to 10.1.5. When the upgrade of the vCenter Server system is complete, upgrade both the VMware Tools and the ESXi host.

  • Deployment size options are not available when migrating or upgrading to vCenter Server Appliance 6.5

    During the migration or upgrade to vCenter Server Appliance 6.5, some deployment sizes are not available for selection in the information table if the required size of your vCenter Server Appliance is greater than the threshold for that deployment size.

    This issue is resolved in this release.

Networking Issues
  • The vSphere ESX Agent Manager (EAM) might stop responding and you might not be able to make EAM API calls to the same agency of affected agent

    If EAM attempts to post an alarm that is not fully initialized due to a null pointer, the EAM server serialization might fail. As a result, EAM might stop responding and you might not be able to make EAM API calls to the same agency of affected agent.

    This issue is resolved in this release.

  • VLANs with custom settings might trigger health check alarms in VMware NSX for vSphere

    In NSX for vSphere environment with enabled health checks, if a logical switch has a VLAN with settings that differ from the default, unnecessary alarms might be triggered.

    This issue is resolved in this release. The fix ignores such alarms. 

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 an SSL protection by using the option Connect to any domain controller, in the vSphere Web Client you might see an error, such as: 
    A vCenter Single Sign-On service error occurred when you try 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. 

vSphere Web Client, vSphere Client, and vSphere Host Client Issues
  • 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.

  • The Service Health status displays Unknown status in the vSphere Web Client

    When you start the health service by using the vSphere Web Client, the Service Health status in the System Configuration section might display Unknown.

    This issue is resolved in this release. 

Guest OS Issues
  • Customizing the static network configuration of virtual machines with SLES 11 and SLES 12 OS might lead to network failures

    Customizing the static network configuration of virtual machines with SLES 11 and SLES 12 OS might lead to network failures. This is because the default static route configured in /etc/sysconfig/network/routes might not be removed after the customization.

    This issue is resolved in this release.

  • Guest OS customization scripts in DASH might not work in VMware vCloud Director due to incompatibility with BASH

    Guest OS customization scripts in DASH might not work in vCloud Director, because some shell commands are incompatible between BASH and DASH.

    This issue is resolved in this release.

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. 

Storage Issues
  • Bulk virtual machine provisioning requests with the ResourceLeaseDurationSec parameter passed through VMware vSphere Storage DRS might fail

    When multiple requests on virtual machine provisioning pass through vSphere Storage DRS with the ResourceLeaseDurationSec parameter specified in the placement spec, vSphere Storage DRS provides initial placement recommendations and allocates space for all of them, blocking the usage of datastore space. This might result in provisioning failures.

    This issue is resolved in this release.

  • vSphere Storage DRS might make just a single recommendation for initial virtual machine placement in a cluster

    For virtual machines with raw device mapping (RDM) virtual disks in a cluster, vSphere Storage DRS might consider the actual mapping file size of RDM disks for existing virtual machines instead of the pointer file size, even though it does not consume any disk space. As a result, vSphere Storage DRS might make just a single recommendation for a suitable datastore when creating new virtual machines in the cluster.

    This issue is resolved in this release.

  • Upload of ISO files to datastores might fail without a warning

    If you log in to the vSphere Web Client with your Active Directory account and attempt to upload an ISO file to a datastore, the operation might fail without an error.

    This issue is resolved in this release. 

  • A wave of Config Update events triggered by a vSphere API for Storage Awareness call might cause out of memory error or irregular API calls

    Before this fix, each Config Update event triggered a full sync with a vSphere API for Storage Awareness provider. As a result, sync threads piled up. In case the number of events of type Config Update was large, this caused out of memory error or irregular triggers of periodic getEvents API calls.

    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.

Backup and Restore Issues
  • Backup of the VMware vCenter Server Appliance might not start if the vmonapi service cannot start while a proxy is configured or not responsive

    While a proxy is configured, or if a proxy is not responsive, the vmonapi service, that provides API to start and stop vCenter Server services, is not running. This blocks backups of the vCenter Server Appliance.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Virtual Machines Management Issues
  • File upload and download, and backup of virtual machines from datastores with names containing non-alphanumeric characters might fail

    Upload and download of files from datastores with names containing non-alphanumeric characters such as “#”,”+” and ”?” might fail if you use the vSphere Web Client or the ESXi Embedded Host Client. Backup of virtual machines might also fail with VDDK error 13.

    Workaround: You can use the vSphere Client as an alternative for file upload and download on vCenter Server systems. For the vSphere Web Client, the ESXi Embedded Host Client, and for the backup of virtual machines issues, you must rename datastores containing non-alphanumeric characters.

Installation and Upgrade Issues
  • You might see a message that no updates are available when patching from vCenter Server 6.5.x to vCenter Server 6.5 Update 2d

    When patching from vCenter Server 6.5.x to vCenter Server 6.5 Update 2d, you might see the following message:
    Latest updates already installed on vCSA, nothing to stage/install

    Workaround: For more information, see VMware knowledge based article 59659

  • The IPv6 loopback address might be replaced by an IPv4 loopback address after a conversion of a vCenter Server Appliance with an external Platform Services Controller

    If you convert instances of vCenter Server Appliance with an external Platform Services Controller into vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode, the loopback address [::1] in pure IPv6 setup might be removed from the /etc/resolv.conf file and an IPv4 loopback address, such as [127.0.0.1], might be added.

    Workaround: After the conversion, manually update the IPv6 loopback address to [::1] in the /etc/resolv.conf file and the /etc/systemd/resolved.conf file.

  • A virtual machine NIC gets a non-sequential list of MAC addresses, even when you allow sequential selection of MAC addresses from MAC address pools

    If you create a base virtual machine with sequential selection of MAC addresses, after a restart of vCenter Server, the order of the network adapters might be nonsequential. If you make a clone from the base virtual machine, the MAC addresses of the clone might also be nonsequential.

    Workaround: You must open the Edit menu of the base virtual machine and click OK to make sure network adapters are sorted as expected before cloning other virtual machines. 

  • Post-update convergence of instances of vCenter Server Appliance with an external Platform Services Controller into vCenter Server Appliance with an embedded Platform Services Controller might fail

    If you update your system to vCenter Server 6.5 Update 2d from 6.5.0 and later, and then converge instances of vCenter Server Appliance with an external Platform Services Controller into vCenter Server Appliance with an embedded Platform Services Controller, convergence might fail with the error:
    MonitorPSCDeployTask execution failed.

    Workaround: Before the conversion, you must:
    1) Navigate to /etc/vmware/install-defaults folder in the vCenter Server node by using Secure Shell.
    2) Open the vmdir.ldu-guid file and copy the content.
    3) Run the command /usr/lib/vmware-vmafd/bin/vmafd-cli set-ldu --server-name localhost --ldu <content copied from Step 2>.
    4) Check the result by running the command /usr/lib/vmware-vmafd/bin/vmafd-cli get-ldu --server-name localhost.

Known Issues from Earlier Releases

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