[root@localhost helm]# kubectl logs -f isilon-controller-0 -n isilon provisioner I1216 17:40:32.391524 1 feature_gate.go:226] feature gates: &{map[]} I1216 17:40:32.391584 1 csi-provisioner.go:98] Version: v1.2.1-0-g971feacb I1216 17:40:32.391594 1 csi-provisioner.go:112] Building kube configs for running in cluster... I1216 17:40:32.398031 1 connection.go:151] Connecting to unix:///var/run/csi/csi.sock W1216 17:40:42.398876 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock W1216 17:40:52.399053 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock E1216 17:40:53.400371 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock. F1216 17:40:53.400470 1 connection.go:91] Lost connection to CSI driver, exiting
[root@localhost helm]# kubectl logs -f isilon-controller-0 -n isilon attacher I1216 17:38:44.424424 1 main.go:91] Version: v1.1.1-0-g0d83c92 I1216 17:38:44.425497 1 connection.go:151] Connecting to unix:///var/run/csi/csi.sock W1216 17:38:54.425740 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock W1216 17:39:04.425755 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock E1216 17:39:06.234790 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock. W1216 17:39:14.426026 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock W1216 17:39:24.426267 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock E1216 17:39:27.273596 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock. W1216 17:39:34.426565 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock
I tried deleting the csi.sock, and reinstalling the driver (helm purge isilon) but come back to this issue. I see the container image gets downloaded successfully but can't figure out this portion:
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 3m55s default-scheduler Successfully assigned isilon/isilon-controller-0 to localhost.localdomain Normal Pulled 3m54s kubelet, localhost.localdomain Container image "quay.io/k8scsi/csi-attacher:v1.1.1" already present on machine Normal Created 3m54s kubelet, localhost.localdomain Created container attacher Normal Started 3m54s kubelet, localhost.localdomain Started container attacher Normal Pulling 3m54s kubelet, localhost.localdomain Pulling image "dellemc/csi-isilon:v1.0.0" Normal Started 3m54s kubelet, localhost.localdomain Started container snapshotter Normal Created 3m54s kubelet, localhost.localdomain Created container snapshotter Normal Pulling 3m54s kubelet, localhost.localdomain Pulling image "quay.io/k8scsi/csi-snapshotter:v1.2.0" Normal Pulled 3m54s kubelet, localhost.localdomain Successfully pulled image "quay.io/k8scsi/csi-snapshotter:v1.2.0" Normal Pulled 3m53s kubelet, localhost.localdomain Successfully pulled image "dellemc/csi-isilon:v1.0.0" Normal Created 3m53s kubelet, localhost.localdomain Created container driver Normal Started 3m53s kubelet, localhost.localdomain Started container driver Normal Started 2m55s (x3 over 3m54s) kubelet, localhost.localdomain Started container provisioner Warning BackOff 2m20s (x3 over 3m11s) kubelet, localhost.localdomain Back-off restarting failed container Normal Created 2m6s (x4 over 3m54s) kubelet, localhost.localdomain Created container provisioner Normal Pulled 2m6s (x4 over 3m54s) kubelet, localhost.localdomain Container image "quay.io/k8scsi/csi-provisioner:v1.2.1" already present on machine
I was able to resolve it by using the "weave net" network on k8s instead of Flannel. For this i had to reinstall the environment (thanks for Florian C).
This can be added in the documentation - that we require a specific pod network.
Also i didn't see the step for 'kubectl create namespace test' which is required to run the tests as they are in the test namespace.
acd13
3 Posts
3521
0
Posted December 18th, 2019 09:00
Yes that's fine.
I was able to resolve it by using the "weave net" network on k8s instead of Flannel. For this i had to reinstall the environment (thanks for Florian C).
This can be added in the documentation - that we require a specific pod network.
Also i didn't see the step for 'kubectl create namespace test' which is required to run the tests as they are in the test namespace.
Anjan