Thick Provision Eager Zeroed named disk is being mounted as thin provision when attached to a VM

Products

• VMware Cloud Director

Issue/Introduction

• Creating Windows Server Failover Cluster(WSFC) within VMware Cloud Director(VCD). 
• Organization VDC where the servers are created has thin provisioning setting disabled.
• VSAN storage policies are used.
• Named disk for the cluster was created as per the steps as in Create a Named Disk in VMware Cloud Director
• The named disk is seen as Thick Provision Eager Zeroed in vCenter(VC).
• Once the disk is attached to the WSFC cluster VMs, the disk seems to be attached as thin provisioned.
• As the disks are attached as thin provisioned, the cluster configuration fails.
• Cluster Validation Wizard completes with the following error:

  "Disk 0 does not support SCSI-3 Persistent Reservations commands needed by clustered storage pools that use the Storage Spaces subsystem. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Contact your storage administrator or storage
vendor for help with configuring the storage to function properly with failover clusters that use Storage Spaces."

Environment

VMware Cloud Director 10.6.x

Cause

This behavior is because the object space reservation is set to Thin provisioning for vSAN storage policy causing the cluster configuration to fail.

Resolution

No action is required from VCD side as the behavior is expected.

For the validation error see,please refer Microsoft Windows Server Failover Cluster Validation Fails: Disk 0 Does Not Support SCSI-3 Persistent Reservations for Storage Spaces Subsystem