-
Notifications
You must be signed in to change notification settings - Fork 537
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
Stuck in Still connecting to unix:///csi/csi.sock
#1301
Comments
We are seeing this as well... I can provide additional logs if needed |
Hi @philnielsen, seems it is the same problem. We will the update the livenessprobe version to 2.12.0 which should have this fix. |
This PR should resolve the issue. Will merge and release by same ECD mentioned above |
The new version is released. Closing the issue, please feel free to open if you are facing the issue still |
@mskanth972 is there any chance of backporting the change to a 1.x release? I'm still reading up on the implications of upgrading to 2.x but it seems like this might be worth backporting |
I am still seeing this issue even in the v2.0.0 release (which includes the new liveness probe sidecar upgrade afaik). I am not able to reproduce it reliably - it just seems to happen occasionally - see logs from a k8s version:
|
We had the same issue with the 3.0.1 chart which uses the 2.0.1 image on k8s 1.29. But while debugging we noticed that the 2.0.1 image was silently removed from Dockerhub, so for now we downgraded the chart back to 3.0.0 which uses the 2.0.0 image which works fine for us. |
/kind bug
What happened?
Sometimes the efs-csi-node pod crashloops forever, leading to a deadlock requiring manual intervention.
What you expected to happen?
If the efs driver never starts, don't schedule pods on the node
How to reproduce it (as minimally and precisely as possible)?
As this only happens intermittently I can't reliably force it to reproduce.
Anything else we need to know?:
kubernetes-csi/livenessprobe#236 I think is the issue, EBS driver fixed it in kubernetes-sigs/aws-ebs-csi-driver#1935 but I'm not sure that EFS driver has picked that up yet? Could this be the same problem? I'm going to test some things and will update this issue with what I find.
Environment
kubectl version
): v1.25.11Please also attach debug logs to help us better diagnose
The text was updated successfully, but these errors were encountered: