Unsolved
19 Posts
0
4579
Installing csi driver
Hi.
I'm trying to set up the CSI driver and connect to Isilon.
Getting this in the logs on the pods which are in CrashLoop.......
time="2021-03-29T09:01:17Z" level=info msg="Configured 'csi-isilon.dellemc.com'" accesspoint=System autoprobe=true insecure=true mode=controller path=/ifs/se1isl001/proj quotaenabled=true
time="2021-03-29T09:01:17Z" level=info msg="************* Synchronizing Isilon Clusters' config **************"
time="2021-03-29T09:01:17Z" level=info msg="removed sock file" path=/var/run/csi/csi.sock
time="2021-03-29T09:01:17Z" level=fatal msg="grpc failed" error="file ('/isilon-configs/config') error: open /isilon-configs/config: no such file or directory"
Any ideas?
Regards,
-Ulf
Flo_csI
2 Intern
2 Intern
•
166 Posts
0
March 29th, 2021 06:00
Hi @Ulfj,
The latest version of the driver (v1.5) introduced the support for multi-array.
That is to say a single instance of the driver can connect to multiple PowerScale/Isilon.
To configure the connectivity (URL & credentials) you have to configure a secret like here : https://github.com/dell/csi-powerscale/blob/master/helm/secret.json
And then create it in Kubernetes with :
kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.json -o yaml --dry-run=client | kubectl replace -f -
I agree that the instructions are unclear and we fix it ASAP.
Let me know if that works.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 29th, 2021 23:00
Hi @Ulfj,
Does the csi-powerscale installation went fine.
Let us know to help you further.
Ulfj
19 Posts
0
March 30th, 2021 01:00
The secret was the problem....figured it out
Now the controller pods start and get ready, but the node pods go in CrashLoop complaining on unable to do reverse dns lookup.
Must the reverse map exist for the node subnet?
Regards,
-Ulf
Ulfj
19 Posts
0
March 30th, 2021 02:00
Got some logs from the nodes.
level=error runid=392 msg="error getting FQDN: 'lookup 54.68.4.10.in-addr.arpa. on 10.4.68.54:53: no such host'" file="/go/src/common/utils/utils.go:266"
-Ulf
Flo_csI
2 Intern
2 Intern
•
166 Posts
0
March 30th, 2021 08:00
Can we make sure that we can access the DNS on 10.4.68.54 from a Pod ?
A good way to debug it, is to use a Pod : https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#create-a-simple-pod-to-use-as-a-test-environment
Then you can do a : nslookup 10.4.68.54
Nit_csi
13 Posts
0
March 30th, 2021 12:00
Hi Ulfj ,
If you still see failure in driver node pod. Let me know which platform you are trying to install driver is it k8s or OpenShift ?
Also, share one of describe node pod logs.
Ulfj
19 Posts
0
March 31st, 2021 01:00
Hi.
I tested to install the dns test container in the namespace I use for the CSI driver and it seems to work.
[a2001008@vm000496 dell_csi]$ kubectl exec -i -t dnsutils -- nslookup kubernetes.default
Server: 172.30.0.10
Address: 172.30.0.10#53
Name: kubernetes.default.svc.cluster.local
Address: 172.30.0.1
If I try to resolve the 10.4.68.54 address.
[a2001008@vm000496 dell_csi]$ kubectl exec -i -t dnsutils -- nslookup 10.4.68.54
54.68.4.10.in-addr.arpa name = 10-4-68-54.machine-config-daemon.openshift-machine-config-operator.svc.cluster.local.
But the Isilon node pod is trying to resolve against 10.4.68.54, which is the pod's IP, which is the same as the nodes, vm, the pod is running on, is that correct?
If I try to resolve against 10.4.68.54 I get the following.
[a2001008@vm000496 dell_csi]$ kubectl exec -i -t dnsutils -- nslookup 10.4.68.54 10.4.68.54
** server can't find 54.68.4.10.in-addr.arpa: NXDOMAIN
Which is the same result as the pod gets.
I also tried to resolve a known address
[a2001008@vm000496 dell_csi]$ kubectl exec -i -t dnsutils -- nslookup 8.8.8.8 10.4.68.54
8.8.8.8.in-addr.arpa name = dns.google.
Which works as expected.
So I'm still not able to run the driver
Regards,
-Ulf
Ulfj
19 Posts
0
March 31st, 2021 01:00
Hi.
It still won't work.
See my previous post.
The cluster is OpenShift 4.7.3.
And here comes a oc describe of a isilon node pod.
Regards,
-Ulf
Nit_csi
13 Posts
0
March 31st, 2021 02:00
Hi
Can you paste me node pod registrar container logs :-
oc logs isilon-node-n5t8t -n isilon -c registrar
Ulfj
19 Posts
0
March 31st, 2021 02:00
Hi.
Here is the log.
Regards,
-Ulf
Ulfj
19 Posts
0
April 5th, 2021 23:00
No more info about this?
Regards,
-Ulf
Flo_csI
2 Intern
2 Intern
•
166 Posts
0
April 6th, 2021 00:00
Hi @Ulfj,
Can you reach out directly to Frank.Gasho@dell.com & florian.coulombel@dell.com so we can have a session and check at your system ?
Thanks
Nit_csi
13 Posts
0
April 21st, 2021 09:00
Hi Ulfj,
Hope this issue is resoled now and we are good to close this.
if not just let us know the latest updates.