vSAN -- Host Client -- Host enters Maintenance Mode with "Ensure accessibility" instead of "Full data migration" or "No Data Migration"

Products

• VMware vSAN

Issue/Introduction

Symptoms:
Symptoms:
When trying to put a host into maintenance mode by using the vSphere Host Client (https://host-name/ui or https://host-IP-address/ui), the following behavior is observed:

• "Ensure accessibility" mode is used even when other options such as  "Full data migration" or "No Data Migration" are selected.
• vSAN host fails to enter maintenance mode when the option "No Data Migration" is selected and when the host is the last active host or one of the last two active hosts in the cluster.

Environment

VMware vSAN 6.7.x
VMware vSAN 6.x

Resolution

This is fixed in ESXi 6.0 P7 (build 9239799), ESXi 6.5 P3 (build 10884925), and ESXi 6.7 U1 (build 10302608).

Workaround:
Instead of using the vSphere Host Client (https://host-name/ui or https://host-IP-address/ui),
use the vSphere Web (Flash) Client or vSphere Client (HTML5) to put the host into maintenance mode.

If vCenter is not available, etc., the host can be put into maintenance mode by using the following commands:
"Full data migration": 
esxcli system maintenanceMode set -e true -m evacuateAllData
"No Data Migration": 
esxcli system maintenanceMode set -e true -m noAction
Warning: Keep in mind that you might experience data loss if a failure occurs on another host in the cluster while the host is in maintenance mode with the noAction option and FTT is set to 1.