You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume from the log that the provisioner sidecar called ControllerGetCapabilities. And the call failed on nil pointer dereference.
Line controllerserver.go:179 contains:
(I am not a real golang dev, but I would expect that it should fail with unknown gRPC method and not panic on invalid memory address or nil pointer dereference.)
Are the conditions above correct?
Or why gRPC called this method even if it has {not⁉} been registered?
The text was updated successfully, but these errors were encountered:
I have misconfigured the driver: set
--component=node
for a controller.And the container failed:
I assume from the log that the provisioner sidecar called ControllerGetCapabilities. And the call failed on
nil pointer dereference
.Line
controllerserver.go:179
contains:seaweedfs-csi-driver/pkg/driver/controllerserver.go
Line 179 in 1a149fe
The log contains
0x0
:The first "argument" is
cs
:seaweedfs-csi-driver/pkg/driver/controllerserver.go
Line 175 in 1a149fe
Therefore, it seems to me that
cs
is nil.But as I used just
--component=node
(without--component=controller
) this service should not be registered:seaweedfs-csi-driver/pkg/driver/server.go
Lines 85 to 90 in 1a149fe
(I am not a real golang dev, but I would expect that it should fail with unknown gRPC method and not panic on
invalid memory address or nil pointer dereference
.)Are the conditions above correct?
Or why gRPC called this method even if it has {not⁉} been registered?
The text was updated successfully, but these errors were encountered: