PDCSI UNSPECIFIED project name logs

Google Cloud Serverless Applications
1

we see the below logs very frequently

/csi.v1.Node/NodeGetVolumeStats called with request: volume_id:"projects/UNSPECIFIED/zones/

project name: UNSPECIFIED

gke version: 1.28.11-gke.1019001

why could project name be UNSPECIFIED ?

2

Hello @Moetazbellah ,

Welcome to Google Cloud Community!

The /csi.v1.Node/ part indicates that the log entry relates to a CSI driver operating within the Kubernetes node environment. While NodeGetVolumeStats part is the name of a specific function or method within the CSI Node service. It allows the Kubernetes cluster to gather key performance metrics about a specific volume attached to a node.

The issue you’re seeing where the project name is appearing as "UNSPECIFIED" in your logs can be attributed to a few possible causes :

  • Incorrect or Missing Metadata : The volume might be provisioned without proper project metadata associated with it. The CSI plugin might be failing to read or interpret the project information from the volume’s metadata. You may check this Overview of using PD CSI driver documentation that fits your configuration for further information.
  • Bug or Compatibility Issue : The problem might be due to a bug or compatibility issue within the version of GKE you’re using and the CSI driver. Check the GKE version and the CSI driver version you’re using. For further reference check this Requirements.
  • Misconfigured or Broken CSI Plugin : The CSI plugin itself might have a bug or misconfiguration that prevents it from correctly identifying the project. The plugin might not be properly configured with the necessary credentials or access rights to retrieve project information.

Here are some basic recommendations for Troubleshooting :

  • Start with Volume Metadata : Verify the volume’s metadata through kubectl describe pv and kubectl describe pvc to confirm the project is properly associated with the volume. You can also check if your PV and PVC has a correct volume path or if it mounted properly.
  • Examine CSI Plugin Configuration : Review the CSI plugin’s configuration files and check for errors or missing settings related to project information.
  • Check for Network Issues : Use kubectl get pods -o wide and kubectl describe pod to identify potential network-related issues affecting the CSI plugin.
  • Check the logs for Persistent Disk CSI Driver : Check this guide on how to check logs further reference.

I hope the above information is helpful.