Cloud builder/Add Domain/Add cluster workflow fails for vSAN ESA in claim vsan disk action.
Article ID: 372832
Updated On:
Products
Issue/Introduction
vSAN ESA workflow fails with error "VSPHERE_AUTO_DISK_CLAIM_FAILED Failed to enable auto claim on cluster".
Environment
VCF
Cause
There are vSAN certified NVMe devices sharing the same PCI ID, thus searching by PCI ID only could result in multiple matched vSAN HCL entries to be found. From vSAN Health Service's perspective, this means that the NVMe device can not be identified (from the vSAN VCG), thus HCL check can not be conducted for the NVMe device.
If it is detected that one NVMe device on a host being used by vSAN has multiple matched HCL entries, this health check will show an alarm (yellow). At the same time, the "NVMe device is VMware certified" will be showing an info status (blue) for the NVMe device.
If such an issue is observed with the VCF setup, auto disk claim can fail for bring up, add domain, add cluster, or add host workflow.
Resolution
Login to vCenter server and claim the disk manually and restart the failed workflow from the SDDC/Bringup.
Or follow resolution mentioned in https://knowledge.broadcom.com/external/article?legacyId=85782 by logging in the vCenter and restart workflow from SDDC/Bringup.
Feedback
