Pods Remain Pending After Local Volume Release Until Pod Deletion/Recreation #504
Description
What happened:
When using a local volume, if a pod that’s using the volume is deleted to free it up, subsequent pods that attempted to use the same volume remain stuck in a pending state. The “FailedScheduling” event with context deadline exceeded from the PreBind "VolumeBinding" plugin is shown. Deleting and recreating the pending pod allows it to schedule successfully.
Event:
58s Warning FailedScheduling pod/pod-98669fbf4-2tjp4 running PreBind plugin "VolumeBinding": binding volumes: context deadline exceeded
What you expected to happen:
Once the local volume is released and available, pods waiting to use it should automatically be scheduled, without requiring manual deletion and recreation.
How to reproduce it:
- Schedule a pod (Pod A) that uses a local volume.
- Attempt to schedule another pod (Pod B) that also requires the same volume—this pod will remain in Pending.
- Delete Pod A, releasing the local volume.
- Pod B stays Pending until it is deleted and recreated, at which point it schedules successfully.
Anything else we need to know?:
Environment:
- CSI Driver version:
2.8.0 - Kubernetes version (use
kubectl version):v1.32.5 - OS (e.g. from /etc/os-release): Garden Linux 1877.0
- Kernel (e.g.
uname -a): Linux 6.6.87-cloud-amd64 - Install tools:
- Others: