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
Windows CSI with iSCSI not reboot proof #342
Comments
Add some details:
|
Welcome! I feel your pain trying to use windows nodes ;) That may need to be startup job handled outside the project to clean those up on boot :( Do you have the logs for the driver when the error was happening? |
I don't found relevant inside csi-driver log from my point of view: zfs-iscsi-democratic-csi-node-windows
csi-proxy:
kubelet log:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
HI,
Thanks for the windows support, I don't like windows but sometime we don't have the choice ;-)
I notice that the CSI don't support windows node reboot without drain (un-plan reboot), and I can reproduce this issue.
State folder in
C:\var\lib\kubelet\plugins\kubernetes.io\csi\org.democratic-csi.iscsi
stay present that block the container to be respawn.In my case just removing the folder
4eb42bec25479cbedfb550e626d766fcd90f97d452b7a11b0bf3331e3ab26cd2
solved the issue and Kubernetes success to reconcile and start the containerMaybe a test on
globalmount
link to see if the disk is mount may help to clean this issue ? or remove every folder on startupHave a good day.
The text was updated successfully, but these errors were encountered: