Grafana Tempo errors with Trident NFS PVCs
Applies to
- NetApp Astra Trident for Kubernetes (ontap-nas-economy driver, version 25.10.0)
- Grafana Tempo application
- Kubernetes (vSphere environment)
Issue
- Grafana Tempo application logs report missing files when using Trident-provisioned NFS Persistent Volumes (PVCs).
- Error messages observed:
level=infots=YYYY-MM-DDThh:mm:ssZcaller=complete_queue.go:125msg="re-queueing block for flushing" block=xxxxyyyy-yyyy-xxxx-zzzz-zyzyzyzyzyzy attempts=2 err="error creating iterator for /var/tempo/traces/env/xxxxyyyy-yyyy-xxxx-zzzz-zyzyzyzyzyzy+env+vParquet4/0000000001: error opening file: open /var/tempo/traces/env/xxxxyyyy-yyyy-xxxx-zzzz-zyzyzyzyzyzy+environment+project/0000000001: no such file or directory"level=warnts=2026-08-21T11:19:10.649663181Zcaller=server.go:1208method=/tempopb.MetricsGenerator/QueryRange duration=xms msg=gRPC err="error opening file /var/tempo/traces/env/yyyyzzzz-xxxx-yyyy-zzzz-xyxyxyxyxy+env+vParquet4/0000000001: error opening file: open /var/tempo/traces/env/yyyyzzzz-xxxx-yyyy-zzzz-xyxyxyxyxy+env+vParquet4/0000000001: no such file or directory"- The directories exist, but the files do not.
- Errors only occur with Trident NFS PVCs; the issue does not appear when using vSphere CSI-provisioned VMDK volumes (local storage)
- Other applications using Trident PVCs do not exhibit this problem
