vSAN -- Proactive Tests -- "VM creation test" ( = Virtual Machine Creation Test )

Products

• VMware vSAN

Issue/Introduction

This article explains the Proactive Test "VM creation test" (= Virtual Machine creation test)
and provides details on why it might report an error.
To access this proactive test:
Select your vSAN Cluster in the vSphere Client -->  Monitor tab -->  Click vSAN -->  Proactive Tests

Reference: Monitoring vSAN Health - Proactive Tests

Environment

VMware vSAN 6.2.x

Resolution

Q: What does the Proactive Tests - VM creation test do?

A: The VM creation test creates a simple tiny Virtual Machine on each host

If the test succeeds, the Virtual Machine gets deleted and it can be concluded that many aspects of vSAN are operational.
It verifies that the management stack is operational on all hosts, vSAN network plumbing is working, creation/deletion
and IO to objects on vSAN is working, etc.
This active test can uncover issues that passive health checks might not detect.
This systematic approach allows vSAN to isolate any faulty hosts and then take steps to resolve issues.


Q: What does it mean when it is in an error state?

A: If the VM creation test fails on a host,
the ability to create or delete objects on the vSAN datastore or remote vSAN datastore if choosing remote vSAN for test in client cluster
might be broken. This can be caused by various factors.
It is recommended that you check the host's accessibility to the vSAN datastore or remote vSAN datastore,
the network and enablement configuration of vSAN, the capacity available on vSAN, etc.
You also can examine the passive health check and review the vSAN performance UI to get a comprehensive understanding of the issue.