-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
CSI can't deregister volume #8285
Comments
Hi @anthonymq sorry about this! The first problem is the sort of thing I'm going to give you some tools to solve with #8251 and #8252.
I can't think of a way that could be related to volumes, but stranger things have happened. I'll see if I can come up with a reproduction. Can you confirm that the command line shows this as well, and that it's not a web UI issue? |
hi @tgross , |
Hey @anthonymq we shipped a |
Wanted to give a quick status update. I've landed a handful of PRs that will be released as part of the upcoming 0.12.2 release:
I believe these fixes combined should get us into pretty good shape, and #8584 will give you an escape hatch to manually detach the volume via |
For sake of our planning, I'm going to close this issue. We'll continue to track progress of this set of problems in #8100. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
I'm having troubles with an amazon efs volume that i deleted before stopping my nomad job who was using it. I can't stop allocations and can't deregister the volume.
![image](https://user-images.githubusercontent.com/1382637/85749124-de92b780-b708-11ea-8642-a36336e076bb.png)
Now I have two allocations that i can't deregister because the clients have been deleted and a volume that has been deleted on aws.
The text was updated successfully, but these errors were encountered: