Symptoms

Following error maybe seen when the VSAN Health check fails: DetailsThe validate_vsan check verifies the health of VSAN cluster to ensure it is healthy. This check also verifies that all VSAN objects in the cluster are healthy. SymptomsOn ACM Server, the /tmp/upgrade_precheck.log shows the following script execution failure: 2022-01-25 12:55:09,669 [validation-5] [INFO] -c.e.i.m.c.u.ProcessBuilderExecutor Traceback (most recent call last): File "/data01/tmp_upgrade_precheck/vsan_validation.py", line 101, in main() File "/data01/tmp_upgrade_precheck/vsan_validation.py", line 94, in main vsan_state_check(vcsaRemote, vcsaIp, vcsaUsername, vcsaPassword, clusterPath) File "/data01/tmp_upgrade_precheck/vsan_validation.py", line 20, in vsan_state_check step1_index = [i for i, s in enumerate(vsanState) if 'Step 1: Check for inaccessible VSAN objects'.lower() in s.lower()][0] + 1 IndexError: list index out of range Note: As per the above error, it is clear that there was an internal health script execution failure while parsing the "vsan.check_state" output. This confirms that the issue exists on PowerProtect Health Check tool.To ensure that the VSAN is healthy, check the vSAN health using ESXi command line using the following command: esxcli vsan health cluster list -w Sample Output from a Healthy System: [root@dp5900esx1:~] esxcli vsan health cluster list -w Health Test Name Status --------------------------------------------------------------------- ---------- Overall health green (OK) Cluster green ESXi vSAN Health service installation (healtheaminstall) green vSAN Health Service up-to-date (healthversion) green Advanced vSAN configuration in sync (advcfgsync) green vSAN daemon liveness (clomdliveness) green vSAN Disk Balance (diskbalance) green Resync operations throttling (resynclimit) green Software version compatibility (upgradesoftware) green Disk format version (upgradelowerhosts) green Network green Hosts with connectivity issues (hostconnectivity) green vSAN cluster partition (clusterpartition) green All hosts have a vSAN vmknic configured (vsanvmknic) green vSAN: Basic (unicast) connectivity check (smallping) green vSAN: MTU check (ping with large packet size) (largeping) green vMotion: Basic (unicast) connectivity check (vmotionpingsmall) green vMotion: MTU check (ping with large packet size) (vmotionpinglarge) green Network latency check (hostlatencycheck) green Data green vSAN object health (objecthealth) green Capacity utilization green Disk space (diskspace) green Read cache reservations (rcreservation) green Component (nodecomponentlimit) green What if the most consumed host fails (limit1hf) green Physical disk green Operation health (physdiskoverall) green Disk capacity (physdiskcapacity) green Congestion (physdiskcongestion) green Component limit health (physdiskcomplimithealth) green Component metadata health (componentmetadata) green Memory pools (heaps) (lsomheap) green Memory pools (slabs) (lsomslab) green Performance service green Stats DB object (statsdb) green Stats master election (masterexist) green Performance data collection (collection) green All hosts contributing stats (hostsmissing) green Stats DB object conflicts (renameddirs) green

Cause

False positive alert due to internal script failure. As per the above error, it is clear that there was an internal health script execution failure while parsing the "vsan.check_state" output. This confirms that this is a false positive alert.

Resolution

This is a known issue on PowerProtect DP Health Check tool version 2.7.2. This failed check can be ignored as false positive.Run the upgrade validation to confirm it passes. NOTE: f the above command returns the Status as green (OK), then proceed with the resolution section. If the Status is RED for one or more parameters, stop following this KB Article..You may also see "diskbalance" and "perfsvcstatus" as yellow in below esxcli command output, we do not expect these warnings to prevent a successful upgrade, ignore, and proceed with upgrade.

Support Cases