Management domain deployment fails during vSAN setup with an error "VSPHERE_AUTO_DISK_CLAIM_FAILED Failed to enable auto claim on cluster"

Products

• VMware SDDC Manager

Issue/Introduction

During SDDC setup the installation workflow fails during vSAN setup. The installation cannot continue without addressing the failure.

/var/log/vmware/vcf/domainmanager/domainmanager.log

YYYY-MM-DDTHH:MIN DEBUG [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Storage pool disks from host host-## are [eui.####, eui.####, eui.####, eui.####, eui.####, eui.####]
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Host host-## does not contribute to the vSAN ESA storage.
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Host host-## does not contribute to the vSAN ESA storage.
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Host host-## does not contribute to the vSAN ESA storage.
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Host host-## does not contribute to the vSAN ESA storage.
YYYY-MM-DDTHH:MIN DEBUG [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-1]  Destroying 2 open views
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  Failed to verify storage pool disks for cluster <Cluster name>
YYYY-MM-DDTHH:MIN ERROR [vcf_dm,685d5dc7783918f789860eb1c7e7493a,09ea] [c.v.v.c.f.p.a.i.ClaimDisksForVsanEsaClusterAction,dm-exec-1]  com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Found host(s) in cluster <Cluster Name> without contributing to storage pool.

Environment

VCF 9.0

Cause

The workflow uses local vSAN-HCL available in SDDC, which is packaged one. This is further synced with vCenter server. Newer version of vSAN-HCL is required.

Resolution

Resolution: Fix is available in upcoming release of VCF 9.0

Workaround: 

Method 1: For deployment with internet connectivity,

• Login to vCenter server and navigate to Configure → vSAN → Update
• Click on "GET LATEST VERSION ONLINE" and wait for "Current database creation date" to get reflect latest one.
• Restart the failed workflow from the vcf-installer ui.

Note: If failure passed one hour then given resolution is not needed as vCenter downloads HCL at one hour interval.

 

Method 2:For deployment without internet connectivity,

• Download vSAN HCL from portal.
• Login to vCenter server and navigate to Configure → vSAN → Update
• Click on "UPDATE FROM FILE" and wait for "Current database creation date" to get reflect updated one.
• Restart the failed workflow from the vcf-installer ui.