You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: treat empty existing mount as stale in ensureMountPoint
On Linux, ensureMountPoint returned mounted=true for any existing mount
whose directory could be listed, without checking whether the mount
actually had content. If a previous NodePublishVolume was interrupted
between mounting the tmpfs and writing provider objects to it (driver
pod killed, context canceled), the kernel-level mount persisted but was
empty. The next NodePublishVolume retry short-circuited at the
"target path is already mounted" branch and reported success on an
empty directory, causing the pod to start with no secrets.
This preserves the same invariant the Windows branch of the function
already enforces - "empty target directory means the caller should
perform a fresh mount" - now correctly on Linux where a stale tmpfs
can persist across driver pod restarts.
Signed-off-by: Gustavo Salvador <gustavo.salvador@outsystems.com>
0 commit comments