VMware released vCenter Server 6.5 Update 1d (Build 7312210) to update few third party packages and to fix plenty of bugs. This release also brings a new icon for vSAN witness appliances.
You can already download the update from my.vmware.com site (login is required).
Note: If you look for VCSA installation instructions, check this article: How to Install VCSA 6.5 (VMware vCenter Server Appliance). If you need update instructions check these articles: Update vCSA using VAMI and Update vCSA using Appliance Shell.
Issues resolved in vCenter Server 6.5 Update 1d
In vCenter 6.5 Update 1d, VMware updated multiple packages:
- Oracle (Sun) JRE 1.8.0_141
- Spring Framework 4.3.9
- OpenSSL 1.0.2l
- Tomcat 8.5.15
- Apache Struts 2.5.13
- Eclipse Jetty 9.2.22
There are also plenty of bugs resolved by the current release:
- vCenter Server might hang when adding an ESXi host to a cluster with associated Host Profile
- Cloning or cold migration might fail when a virtual machine picks an invalid host
- VMware vCenter Server Appliance configured with VMware vCenter Server High Availability might fail after an upgrade to 6.5 Update 1
- Select deployment size page of vCenter Server Appliance Installer might show irrelevant size values
- After upgrade to vCenter Server 6.5 the Hardware Status tab in vSphere Web Client might show error that no host data is available
- Default settings for root password expiration might be restored after minor upgrades
- The Email Address field in the vSphere Web Client alarm configuration wizard does not accept certain top level domains
- vCenter Server might fail with in attempt to use OptionManager
- Agent virtual machines running on an ESXi host are powered off when the host enters a maintenance mode and cannot be restarted
- Domain join might fail if concatenation of domain names in Active Directory environment with many trusted domains exceeds string length limit
- vCenter Server might lose connectivity in attempt to mount or unmount an ISO image
- VPXD might fail due to a possible circular dependency in VMware DRS clusters with enabled VMware Distributed Power Management
- Upgrade and installation of IO filters might fail if the path to the IO Filter VIB is different from the original url
- SNMP manager of vCenter Server might fail to receive traps older than 497 days from a vCenter Server Appliance
- Log in to vSphere Web Client might fail if the fully qualified domain name of a vCenter Server contains the string .swf
- Attempt to export all matching events using vSphere Web Client might deliver a limited list of events
- Host profile might fail to extract after import of a VMware vSphere Distributed Switch from a backup file
- vNICs of virtual machines might lose connection after a refresh of VMware Horizon view pool
- vMotion of virtual machines with imported ephemeral port groups might fail as ports are not created after migration
- vCenter Server does not accept SNMP users with non-alphanumeric characters
- vSphere Web Client might show error in vSphere Distributed Switch topology after a restart of vpxd due to outdated Link Aggregation Groups data
- Unlimited calls to list recent tasks in vSphere Client might lead to system outage
- Login of Active Directory domain user accounts ending with a dollar sign fails on vCenter Server and ESXi hosts
- Attempts to join Active Directory domains fail intermittently with error LW_ERROR_KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN
- Identity source edit for LDAP connections might fail if primary server stops responding
- vSphere Web Client might not properly display storage devices after EMC Powerpath 6.0.1. installation
- Datastores might falsely appear as incompatible for a storage policy that includes I/O filter rules
- Map Disk Region task might fill up the vCenter Server database task table
- Memory leak in Ehcache might cause VMware Performance Charts service to fail and large java_pid.hprof files might pile in the storage
- vSphere Web Client might show wrong host datastores when you select the option Connect to CD/DVD image on a datastore
- VPXD might fail if you try to use a Host Profile from a host with version lower than vSphere ESXi 5.1
- vSAN license expiration alerts might continue even if vSAN is disabled
- vCenter Server Content Library service might fail to start after an upgrade
- VM operations triggered while an ESXi host enters maintenance mode might fail without a warning
- Attempts to edit a scheduled task for virtual machine snapshots via the vSphere Web Client might fail with error 1009
- vCenter Sever might not propagate updated data for CPU and memory reservation to vCloud Director
- Mass provisioning of virtual machines in VMware vCloud Director for Service Providers triggers multiple alarms on vCenter Server
- vCenter Server might block restricted user accounts to perform migrations across vCenter Server systems
- vCenter Server might fail due to an excessive use of resources in concurrent calls to the blocking methods of the PropertyCollector
- Creation of new deploy rules from a customized image might fail in vSphere ESXi Image Builder
- vSAN iSCSI messages might flood the Tasks view of vSphere Web Client
- vSAN Health Service logs might eat up all log storage space in vCenter Server on Windows
- vSphere Update Manager baselines might change from patch to upgrade when only one node in a cluster is remediated
For complete details, check the release notes.
Happy testing 🙂