Snapshotter container stuck on connecting

[igorgonibm]

We use tag 1.2.2

In logs the following message appears endless number of times:
connection.go:170] Still connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
The logs are:
main.go:89] Version: v1.2.2-0-gd5da3c1e
Connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
connection.go:170] Still connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
connection.go:170] Still connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
connection.go:170] Still connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
....

The socket is correct since we have another sidecar container csi-attacher which uses the same socket and it works and sends GRPC requests.
main.go:95] Version: v1.2.1-0-g6dce9d7
connection.go:151] Connecting to unix:///var/lib/csi/sockets/pluginproxy/csi.sock
common.go:111] Probing CSI driver for readiness
connection.go:180] GRPC call: /csi.v1.Identity/Probe

[xing-yang]

What is the k8s version?

[igorgonibm]

k8s 1,14

[zhucan]

@igorgonibm @xing-yang It works well. k8s version: v1.14.2

[zhucan]

@igorgonibm Can you paste the yaml about the snapshotter？

[igorgonibm]

The full version is: GitVersion:"v1.14.7"
@zhucan which yaml is it? We just define container given csi-snapshotter image path from operator code.

[zhucan]

setup-csi-snapshotter.yaml

[igorgonibm]

@zhucan We didn't use such file.. Where can I get it? Is it something in csi-snapshotter sources?

[zhucan]

@igorgonibm How do you deploy snapshotter? Isn't it through set-csi-snapshotter yaml？

https://github.com/kubernetes-csi/external-snapshotter/tree/v1.2.2/deploy/kubernetes

[igorgonibm]

@zhucan we did it according to https://github.com/kubernetes-csi/external-snapshotter. There was nothing about such yaml. We create snapshotter container from code not yaml.

[zhucan]

@igorgonibm I don't understand what you mean. If you deploy the sidecar not through the yaml,
How did you specify the socket path for the snapshotter？

[zhucan]

like this？

[igorgonibm]

@zhucan yes exactly. We just give another socket path (as specified above)

[zhucan]

@igorgonibm I have not tried this way, why not deploy snapshotter with yaml？

[igorgonibm]

@zhucan this is just the way our deployment works. We do it using csi operator in go-lang code.

[xing-yang]

I tested csi-snapshotter v1.2.2 image on k8s 1.14.7. It worked for me.