Horizon 7: Entering maintenance mode with "No data evacuation" in a Horizon linked clone environment running on vSAN, can cause some VMs to go inaccessible.
Article ID: 367540
Updated On:
Products
Issue/Introduction
When entering maintenance mode with "No data evacuation" in a Horizon linked clone environment running on vSAN, some VMs can become inaccessible.
Cause
In linked clone environments, a vmdk file of the Linked clone VM refers to a vmdk file of the golden image VM.
When hosts exit maintenance mode and if the Linked clone VM becomes accessible before the golden image vmdk, it could become inaccessible because of the dependency of the vmdk between the Linked clone and the golden image.
Even after the golden image vmdk becomes accessible, the host may not reload the Linked clone VM.
Resolution
When doing maintenance tasks on hosts in a Linked clone environment running on vSAN, it is recommended the host enter maintenance mode with "Ensure data accessibility" or "Full data migration".
Note: This behaviour can manifest in scenarios where best practice migration is not possible, The default evacuation mode is Ensure data accessibility/ Evacuate all data mode and VM inaccessibility may arise from other migration techniques.
Please see these resources to assist with planning and preparations for VSAN upgrade:
- vSAN upgrade requirements (2145248)
- VMware vSAN upgrade best practices (2146381)
- Administering VMware Virtual SAN - Before You Upgrade Virtual SAN
Work around
Restart hostd service on all hosts in the cluster:
# /etc/init.d/hostd restart
Feedback
