7 Posts
0
1672
April 13th, 2021 00:00
isilon-node pods ends up in crash loop
Hi
Just set up the CSI Driver on OpenShift 4.7, controllers start up without a hitch. However the isilon-node-* pods ends up in a crash loop with the following error message:
[lars@l02umesmg0998 ~]$ oc logs isilon-node-msccw -n isilon -c driver --tail=200
time="2021-04-13T07:09:12Z" level=debug msg="enabled context injector"
time="2021-04-13T07:09:12Z" level=debug msg="init req & rep validation" withSpec=false
time="2021-04-13T07:09:12Z" level=debug msg="init implicit req validation" withSpecReq=false
time="2021-04-13T07:09:12Z" level=debug msg="init req validation" withSpecReq=true
time="2021-04-13T07:09:12Z" level=debug msg="enabled request ID injector"
time="2021-04-13T07:09:12Z" level=debug msg="enabled request logging"
time="2021-04-13T07:09:12Z" level=debug msg="enabled response logging"
time="2021-04-13T07:09:12Z" level=debug msg="enabled spec validator opt: request validation"
time="2021-04-13T07:09:12Z" level=debug msg="enabled serial volume access"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x123dba6]
goroutine 1 [running]:
github.com/sirupsen/logrus.(*Entry).Logf(0x0, 0x2, 0x1780feb, 0x1c, 0xc00008da88, 0x1, 0x1)
/go/pkg/mod/github.com/sirupsen/logrus@v1.6.0/entry.go:332 +0x26
github.com/sirupsen/logrus.(*Entry).Errorf(...)
/go/pkg/mod/github.com/sirupsen/logrus@v1.6.0/entry.go:362
github.com/dell/csi-isilon/common/utils.ParseArrayFromContext(0x1952840, 0xc0003c0d20, 0x1778d7f, 0x16, 0x0, 0x0, 0x0)
/go/src/common/utils/utils.go:106 +0x1b7
github.com/dell/csi-isilon/service.(*service).initializeServiceOpts(0xc0001400c0, 0x1952840, 0xc0003c0d20)
/go/src/service/service.go:175 +0x3a5
github.com/dell/csi-isilon/service.(*service).BeforeServe(0xc0001400c0, 0x1952840, 0xc0003c0d20, 0xc000546000, 0x1950400, 0xc0003c0c30, 0x0, 0x0)
/go/src/service/service.go:404 +0x45
github.com/dell/gocsi.(*StoragePlugin).Serve.func1()
/go/pkg/mod/github.com/dell/gocsi@v1.2.3/gocsi.go:251 +0xc26
sync.(*Once).doSlow(0xc000546088, 0xc00008dd90)
/usr/local/go/src/sync/once.go:66 +0xec
sync.(*Once).Do(...)
/usr/local/go/src/sync/once.go:57
github.com/dell/gocsi.(*StoragePlugin).Serve(0xc000546000, 0x1952840, 0xc0003c0d20, 0x1950400, 0xc0003c0c30, 0x0, 0x0)
/go/pkg/mod/github.com/dell/gocsi@v1.2.3/gocsi.go:216 +0xc5
github.com/dell/gocsi.Run(0x19527c0, 0xc0000a8008, 0x1778ef5, 0x16, 0x17a66e5, 0x32, 0x180dfe2, 0x475, 0x19421c0, 0xc000546000)
/go/pkg/mod/github.com/dell/gocsi@v1.2.3/gocsi.go:130 +0x55b
main.main.func1(0x19527c0, 0xc0000a8008)
/go/src/main.go:41 +0x90
main.main()
/go/src/main.go:50 +0x382
Anyone got any ideas?
Thar_J
42 Posts
1
April 14th, 2021 00:00
Hi
Wanted to clarify the way you have provided the custom network in the sample file .
Kindly check if you have provided the custom network in the sample file this way :
- name: X_CSI_ALLOWED_NETWORKS
value: "192.168.1.0/24"
Change to this format mentioned below:
- name: X_CSI_ALLOWED_NETWORKS
value: "[192.168.1.0/24]"
Try installing the driver post changes with an uninstall and reinstall and let us know about the installation.
swull
7 Posts
0
April 14th, 2021 23:00
That was it! Very nice work
I would NOT have figured that out on my own.
Thar_J
42 Posts
0
April 15th, 2021 02:00
Hi Swull
Great to hear that , hope you were able to install the driver now.
Cheers.
Thanks
Thar_J
swull
7 Posts
0
April 15th, 2021 03:00
I was, thanks
Now I get stuck on some "authorization required".
But it is most likely a role missing from my user.
Not sure which one tho, but we'll see.
Thar_J
42 Posts
0
April 15th, 2021 22:00
Hi Skull
Could you please provide us more clarity on where are you seeing the Authorization required issue.
Are you trying to install the driver with other user than root or admin.
Thanks
Thar_J
swull
7 Posts
0
April 22nd, 2021 00:00
Hi
No, what i'm facing with that is that i set the IP as the hostname for the cluster. (I can't really figure out from the documentation what IP i should set the configuration against).
So what happened then when using the FQDN is that it jumps between the nodes, triggering what i'm assuming is some kind of XSS protection.
So when I set it towards one of the node IPs, everything works. But this seems like a very vulnerable SPOF solution.