vSAN Data Provider has failed with error 'error.query.coreApiMismatch: Failed to convert the QuerySpec to internal representation.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• vSAN plug-in missing in the vSphere web client

• The following error is noticed in the vSAN Cluster and on the vSAN Services tab.

  error.query.coreApiMismatch: Failed to convert the QuerySpec to internal representation. Could not qualify property: 'isVsanPMemEnabled'. It is possible that the property is misspelled or a connection to a certain Data Provider has failed. Please check the logs for other errors.

or 

 error.query.coreApiMismatch: Failed to convert the QuerySpec to internal representation. Could not qualify property: 'name'. It is possible that the property is misspelled or a connection to a certain Data Provider has failed. Please check the logs for other errors.

Environment

VMware vSAN 8.0.x

VMware vSAN 7.0.x

Cause

• This issue arises when the vCenter Machine SSL certificate expires.

Follow the vCenter UI path to validate: 

• Click on three lines [hamburger menu] > Administration >  Certificate > Certificate Management

 

• Running Lookup Service Doctor (lsdoctor) on the vCenter server indicates the vCenter certificate has expired. 

Example : 

root@testvc [ /tmp/lsdoctor-240201 ]# python lsdoctor.py -l
    ATTENTION:  You are running a reporting function.  This doesn't make any changes to your environment.
    You can find the report and logs here: /var/log/vmware/lsdoctor
2025-01-13T07:40:31 INFO main: You are reporting on problems found across the SSO domain in the lookup service.  This doesn't make changes.
2025-01-13T07:40:32 INFO live_checkCerts: Checking services for trust mismatches...
2025-01-13T07:40:32 WARNING live_checkCerts: Expired certificate found for node testvc.test.com!
2025-01-13T07:40:32 INFO generateReport: Listing lookup service problems found in SSO domain
2025-01-13T07:40:32 ERROR generateReport: default-first-site\testvc.test.com (VC 7.0 or CGW) found Certificate(s) Expired: Regenerate the MACHINE_SSL_CERT.  If Legacy Endpoints, check STS_INTERNAL_SSL_CERT.

Refer KB # 320837 on how to use the 'lsdoctor' Tool

Resolution

Follow the article to regenerate the vCenter certificate to resolve the issue.

Regenerate vSphere 6.x, 7.x, and 8.0 certificates using self-signed VMCA.