vSAN File Service with vSAN RDMA enabled is in an unhealthy state after upgrading from 7.x to 8.x

Products

• VMware vSAN

Issue/Introduction

• After upgrading vSAN environment to 8.x vSAN File Service is in an unhealthy state
• vSAN RDMA is enabled
  
  

Environment

VMware vSAN 8.x
vSAN File Service
vSAN RDMA

Cause

When vSAN RDMA is enabled with vSAN File Service, the vdfsd-proxy fails to query the cluster encryption state resulting in vSAN File Service failing to re-enable properly after the upgrade.

Resolution

vSAN Engineering is aware of this issue and working on a fix for future release.

Workaround

If the environment was already upgraded and vSAN File Service is in an unhealthy state

1. SSH to all hosts in the cluster and run esxcli system secpolicy domain set -l warning -n vdfsProxyDom (This will allow the vdfsd-proxy to refresh the config store and get the correct cluster encryption status.)
2. Restart the vdfsd-proxy by running pkill vdfsd-proxy on all hosts to get the correct cluster encryption status

If further assistance is required open a case with vSAN Support.