This is a known issue fixed in ESXi 6.5 P03.
Build and Download details can be found in the release notes here:
VMware ESXi 6.5, Patch Release ESXi650-201810002This issue is also fixed in ESXi 6.7 U1.
Upgrade both vCenter and all hosts in the cluster to build 10884925 or higher. It is highly recommended that you upgrade to the latest available 6.5 U3 or 6.7 U3 patch if possible.
Workaround:
As a temporary solution, restarting vsanmgmtd and the management agents may resolve the issue.
Login to the ESXi CLI via Console or SSH as root and run the below commands on all hosts that are currently impacted:
$ /etc/init.d/vsanmgmtd stop
$ /etc/init.d/vsanmgmtd start$ /etc/init.d/hostd stop
$ /etc/init.d/hostd start$ /etc/init.d/vpxa stop
$ /etc/init.d/vpxa start