Control: severity -1 important Hello Nicolas,
thanks for the pointer. On Tue, Apr 12, 2022 at 11:35:01AM +0200, Nicolas Noirbent wrote: > Since the upgrade to version 1.20.5+really1.20.2-1.1, using "kubernetes > config use-context" to > switch context systematically triggers SIGSEGV: > > % kubectl config use-context dev-go-cell-001 > unexpected fault address 0x0 > fatal error: fault > [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x46421f] > […] > > This also obviously affects kubectx and kubens (which uses kubectl config > use-context); however it > does not preclude from manually setting a context / namespace when running > regular kubectl > commands, e.g.: > > % kubectl --context dev-go-cell-001 --namespace hello-world get pods > NAME READY STATUS RESTARTS AGE > […] > > Downgrading to 1.20.5+really1.20.2-1 fixes the issue, so I suspect this has > something to do with > the switch to golang 1.18 done to fix > #https://bugs.debian.org/cgi-bin/bugreport.cgi?1000980 Commenting here as I did the NMU to fix #1000980: Confirmed, and for me the segfault looks exactly the same. I'm raising the severity due to the segfault, but I'm not raising to RC-level as most(?) functionality remains available, at the cost of ease of use. Or at least that is what I tedn to believe at the moment. Shengjing Zhu do you maybe have more insights into this issue? Cheers, Flo
signature.asc
Description: PGP signature
