-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Pod stuck in Terminating if a configmap is mounted with subPath #771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can replicate this and see the error.
|
Are there more logs associated? What happens if you try to unmount it manually ?
|
I'm pretty sure I know what this is, just ran out of time to patch it yesterday and then today we've had some upstream things to patch :-) There are more logs yes, but that's the relevant part. If you run umount manually you won't get a different result. This is a bug in kind. |
This should be fixed (and probably other things!) with the latest version, please let me know if you see this again. We'll be cutting a new release soon but need to check on some unrelated issues 😅 |
Also: Thanks for reporting this, and for the detailed report and minimal reproducer! |
What happened:
When I create a pod which includes a configmap volume and if the volume mount uses a
subPath
it's not possible delete the Pod, it stays inTerminating
forever.This is a weird one and it only seems to happen on Mac, colleagues on Linux were unable to reproduce, so it's possibly a docker issue.
What you expected to happen:
I expected the Pod to be deleted after a delete call.
How to reproduce it (as minimally and precisely as possible):
With the following yaml as
example.yaml
:Run:
After a while it's possible to see that the pod is still Terminating:
Anything else we need to know?:
The problem only seems to happen on MacOS, on Linux I was unable to reproduce, the pod is successfully deleted.
Environment:
kind version
):kubectl version
):docker info
):/etc/os-release
):The text was updated successfully, but these errors were encountered: