In OCP 4.15.20, vSphere problem detector pod is showcasing cache log errors: 
2025-03-07T07:35:23.275522394Z I0307 07:35:23.275422       1 datastore.go:329] checking datastore ds:///vmfs/volumes/5efefe8b-aaaa-bbbbb-cccccc-dddd/ for permissions
2025-03-07T07:35:23.275795140Z E0307 07:35:23.275770       1 cache.go:252] couldn't find Datastore with reference Datastore:datastore-12345 in datacenter DC-NAME
2025-03-07T07:35:23.275795140Z E0307 07:35:23.275786       1 datastore.go:362] fetching datastore Datastore:datastore-12345 failed: couldn't find Datastore with reference Datastore:datastore-12345 in datacenter DC-NAME


The first log line is checking the permissions for datastore which corresponds to default-datastore in cloud-provider-config configmap in openshift-config namespace. 

After this log line, couldn't find Datastore with reference Datastore errors are coming for in total 9 datastores. These 9 different datastore object IDs are not same with datastore ID of default-datastore for which permission check was started. 

So, how these other datastore object IDs are coming into the picture which might not be related to OCP? 

All OCP node disks and PV disks are only coming from total 2 datastores. i.e. 1 datastore from which OCP node OS disk is coming and other one is default-datastore from which PV disks are coming.

With vSphere user configured at OCP, default-datastore is accessible. 

tried to restart the vsphere-problem-detector pod to resync the cache but these logs are coming with new pod as well. 

 OCP 4.15.20 

    Always

    1.
    2.
    3.
    

    vSphere problem detector pod is showing error logs for datastore.

    vSphere problem detector pod should check default-datastore for permission check properly and it should not showcase errors for other datastore object IDs which are not related to that specific OCP cluster.