-
Notifications
You must be signed in to change notification settings - Fork 85
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
[BUG] driver name csi.juicefs.com not found in the list of registered CSI drivers #1191
Comments
There exists the same issue #751 is also in unclosed state |
juicefs-csi-node-slrlb is deployed on the machine where the pod is scheduled |
Here are some details: |
Can you check if the CSI Node started(1122 08:05:28.125702) after application pod? Also, can you provide the log of kubelet? @YaAYadeer |
Yes,the CSI Node is running
4.
|
Besides, when I use |
Can you provide the log of kubelet? |
I grep juice of the kubelet log
|
Can you grep the log around the time CSI Node started? |
The status of the csi node is normal, can the sign of successful CSI registration not be judged only by get drivers? This problem really bothers me, because it hinders my other work. Could you please help me check the problem |
|
No useful information can be obtained from the logs you provided, because you grep
Let’s recheck the environment. Be sure to run the exact command:
The normal kubelet should contain |
|
I use helm to deploy the pod, I must use kubectl so that the log contains item "Register new plugin with name: csi.juicefs.com" ? |
Please check Mount Pod, see: https://juicefs.com/docs/csi/troubleshooting/#check-mount-pod closing |
What happened:
I deployed CSI successfully and created PV and PVC. However, I encountered an error while creating a pod:
kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name csi.juicefs.com not found in the list of registered CSI drivers.
But I use the command "kubectl get csidrivers.storage.k8s.io". I find csi.juicefs.com is in the list.
Besides,I use
kubectl logs -n kube-system juicefs-csi-node-xxx juicefs-plugin --tail 100
kubectl logs -n kube-system juicefs-csi-node-xxx juicefs-plugin --tail 100
to checked the logs,but find nothing wrong.What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: