microk8s icon indicating copy to clipboard operation
microk8s copied to clipboard

Outdated Addons

Open olandodeflexy opened this issue 9 months ago • 1 comments

Summary

My CSI-provisioner container crashed with the error below

unexpected fault address 0x8eb180
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x2 addr=0x8eb180 pc=0x8eb180]

goroutine 1 [running, locked to thread]:
runtime.throw(0x1bc4a84, 0x5)
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/panic.go:1117 +0x72 fp=0xc000073a08 sp=0xc0000739d8 pc=0x436fb2
runtime.sigpanic()
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/signal_unix.go:741 +0x268 fp=0xc000073a40 sp=0xc000073a08 pc=0x44d828
golang.org/x/net/trace.init()
	/workspace/vendor/golang.org/x/net/trace/events.go:153 fp=0xc000073a48 sp=0xc000073a40 pc=0x8eb180
runtime.doInit(0x292f5a0)
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/proc.go:6265 +0xec fp=0xc000073b98 sp=0xc000073a48 pc=0x44726c
runtime.doInit(0x2935be0)
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/proc.go:6242 +0x72 fp=0xc000073ce8 sp=0xc000073b98 pc=0x4471f2
runtime.doInit(0x292b560)
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/proc.go:6242 +0x72 fp=0xc000073e38 sp=0xc000073ce8 pc=0x4471f2
runtime.doInit(0x2933b80)
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/proc.go:6242 +0x72 fp=0xc000073f88 sp=0xc000073e38 pc=0x4471f2
runtime.main()
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/proc.go:208 +0x205 fp=0xc000073fe0 sp=0xc000073f88 pc=0x4397a5
runtime.goexit()
	/go/pkg/csiprow.XXXXDgfhaa/go-1.16/src/runtime/asm_amd64.s:1371 +0x1 fp=0xc000073fe8 sp=0xc000073fe0 pc=0x46c9c1

I reported the issue to openebs/mayastor and they indicated an outdated provisioner. Microk8s is using registry.k8s.io/sig-storage/csi-provisioner:v2.2.1 but the current version is v3.5.0 I was wondering if there are plans to update the outdated addons to help us stay up to date.

What Should Happen Instead?

To get updated addons on a regular bases.

olandodeflexy avatar Mar 17 '25 16:03 olandodeflexy

Hey @olandodeflexy

We'll try reproducing the issue and see if we an update to the mayastor addon fixes it. We'll keep the issue updated with any news, many thanks!

berkayoz avatar Mar 19 '25 09:03 berkayoz