-
Notifications
You must be signed in to change notification settings - Fork 148
socket connection failed on windows node #491
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
what's the
and can you also run |
log for smb is as follows. I am not able to understand what IP is it trying to reach. I have deleted all pvc related to this driver. It may be possible that I scaled the cluster down to one windows node and this is IP of the other node which is no longer part of scaleset. root@CAPZ-Management:/home/bmadministrator/.kube# kubectl --kubeconfig=config logs csi-smb-node-win-6npfj -n kube-system
|
I can also kind of reproduce this in local micro k8s cluster with windows node running Calico. Error from server: Get "https://win-7ivb3hcarnh:10250/containerLogs/kube-system/csi-smb-node-win-q4cwq/node-driver-registrar": dial tcp: lookup win-7ivb3hcarnh: Temporary failure in name resolution |
I still have the original issue on the azure cluster having windows node pool that has been created with CAPZ. |
I see this error, could you add
|
Thank you, I will check and update after 2 weeks. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
Smb driver keeps crashing and restarting on windows node.
E0602 15:05:03.340095 6944 connection.go:132] Lost connection to unix://C:\csi\csi.sock.
kubectl logs csi-smb-node-win-6npfj node-driver-registrar -n kube-system
I0602 15:01:56.103598 6944 main.go:166] Version: v2.5.0
I0602 15:01:56.477717 6944 main.go:167] Running node-driver-registrar in mode=registration
I0602 15:01:56.478467 6944 main.go:191] Attempting to open a gRPC connection with: "unix://C:\\csi\\csi.sock"
I0602 15:02:03.853302 6944 main.go:198] Calling CSI driver to discover driver name
I0602 15:02:03.864755 6944 main.go:208] CSI driver name: "smb.csi.k8s.io"
I0602 15:02:03.865660 6944 node_register.go:53] Starting Registration Server at: /registration/smb.csi.k8s.io-reg.sock
I0602 15:02:03.865988 6944 node_register.go:62] Registration Server started at: /registration/smb.csi.k8s.io-reg.sock
I0602 15:02:03.868307 6944 node_register.go:92] Skipping HTTP server because endpoint is set to: ""
I0602 15:02:04.049487 6944 main.go:102] Received GetInfo call: &InfoRequest{}
I0602 15:02:04.050576 6944 main.go:109] "Kubelet registration probe created" path="C:\var\lib\kubelet\plugins\smb.csi.k8s.io\registration"
I0602 15:02:04.070355 6944 main.go:120] Received NotifyRegistrationStatus call: &RegistrationStatus{PluginRegistered:true,Error:,}
E0602 15:05:03.340095 6944 connection.go:132] Lost connection to unix://C:\csi\csi.sock.
What you expected to happen:
Smb driver on windows node should run without restarts.
How to reproduce it:
Create a workload cluster using capz with a windows nodepool in it such that windows node is ready
Install CSI Proxy and CSI Driver SMB including installing on windows node
check the logs for the csi-smb-node-win-xxxxx node-driver-registrar
Anything else we need to know?:
Environment:
CSI Driver version: master
Kubernetes version (use
kubectl version
): 1.23.6OS (e.g. from /etc/os-release): Jammy Jellyfish
Kernel (e.g.
uname -a
):Linux CAPZ-Management 5.15.0-27-generic fix: Add release-tools subtree #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/LinuxInstall tools: capz kubectl helm
Others:
The text was updated successfully, but these errors were encountered: