Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
occasional "The process cannot access the file because it is being used by another process" on pod teardown on Windows 1.15.9 #89484
Running deployment was updated, forcing creation of new pods. On pod teardown pod directory could not be deleted. As a result deployment rollout did not finish.
E0325 10:09:45.952766 5284 nestedpendingoperations.go:270] Operation for ""kubernetes.io/secret/b84b370d-3439-41ed-9091-ec0d5cb70edb-default-token-lzg9s" ("b84b370d-3439-41ed-9091-ec0d5cb70edb")" failed. No retries permitted until 2020-03-25 10:11:47.9527665 -0400 EDT m=+4297553.319146501 (durationBeforeRetry 2m2s). Error: "UnmountVolume.TearDown failed for volume "default-token-lzg9s" (UniqueName: "kubernetes.io/secret/b84b370d-3439-41ed-9091-ec0d5cb70edb-default-token-lzg9s") pod "b84b370d-3439-41ed-9091-ec0d5cb70edb" (UID: "b84b370d-3439-41ed-9091-ec0d5cb70edb") : remove c:\var\lib\kubelet\pods\b84b370d-3439-41ed-9091-ec0d5cb70edb\volumes\kubernetes.io~secret\default-token-lzg9s: The process cannot access the file because it is being used by another process."
Manually restarting kubelet and kube-proxy released lock/fixed the issue
What you expected to happen:
Note this issue does not occur frequently. Maybe happens to 1 out of 50 deployment updates randomly
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: