vSAN ESA Storage Policy for Virtual Machine cannot be changed back to RAID6 after previous change to RAID1/5

Products

• VMware vSAN

Issue/Introduction

• Virtual Machine(s) are deployed using a vSAN ESA RAID6 Policy and later changed to either RAID1 or RAID5 but a subsequent change to the original RAID6 policy fails.

Environment

• 2 Node Robo vSAN ESA cluster (using nested Fault domains)
• ESXi 8.0U3 P08 (24859861)

Cause

• Attempt to reapply the RAID6 Policy fails due to incorrect number of Lower Fault Domains detected. 
• Lower Fault Domain is incorrectly detecting Hosts as opposed to disks in storage pool of a host.

 

• Error similar to below can be seen in Task View of vCenter UI: 

Resolution

• Currently there is no solution for this problem. Broadcom Engineering is are aware of the issue and fix is scheduled to be made available in the next release of vSphere. 
   

 

• Workaround:
• Any Virtual Machine requiring immediate change of Storage Policy to RAID6 should be cloned with RAID6 selected as Storage Policy for the clone.