- vSphere Web Client might not properly display storage devices after EMC Powerpath 6.0.1. installationvSphere Web Client might not properly display storage devices after EMC Powerpath 6.0.1 installation if the ESXi host has only LUNs and the host is set up to boot from a SAN.This issue is resolved in this release.
- Datastores might falsely appear as incompatible for a storage policy that includes I/O filter rulesWhen you create or edit an existing storage policy, containing I/O filter common rules, and while checking for storage compatibility, you might observe messages like:
Datastore does not match current VM policyor
Datastore does not satisfy compatibility since it does not support one or more required properties
Some of the datastores that you expect to be compatible, might appear in the incompatible list when you are checking for storage compatibility. This might also happen when you provision a virtual machine with a storage policy, containing I/O filter rules.This issue is resolved in this release.
- Map Disk Region task might fill up the vCenter Server database task tableThe Map Disk Region task might alone fill up the
vpx_tasktable in the vCenter Server database, which might cause vCenter Server to become unresponsive or other performance issues.
- vSAN iSCSI messages might flood the Tasks view of vSphere Web ClientIf you upgrade a vSAN cluster from a vSphere 6.0 environment to a vSphere 6.5 environment, a message like
Edit vSAN iSCSI target service in clustermight flood the Tasks view in the vSphere Web Client, even if the vSAN iSCSI feature is not enabled in this cluster.This issue is resolved in this release.
- New icon for vSAN witness appliancesThis release introduces a new icon for vSAN witness appliances. When you deploy a vSAN witness appliance, you will see a nested host with a new icon in the UI, which indicates that this host can only be used as a witness in a stretched cluster.This issue is resolved in this release.
- vSAN Health Service logs might eat up all log storage space in vCenter Server on WindowsvSAN Health Service logs might eat up all log storage space in vCenter Server on Windows if log rotation coincides with a running task for collecting support bundle or phone home data for Customer Experience Improvement Plan (CEIP).This issue is resolved in this release.
- vSphere Update Manager baselines might change from patch to upgrade when only one node in a cluster is remediatedvSAN build recommendation for system baselines and baseline groups for use with vSphere Update Manager might not work if there is a vCenter Server system-wide http proxy. With this fix, vSAN build recommendations in a system-wide http proxy set up are as available and consistent as the vSAN build recommendations created with direct Internet connection.