Hide Forgot
This panic appears every few minutes in the provided run (hile looking for something else). It appears to be related to one form of pod shutdown. Setting to urgent because it may be preventing shutdown https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-aws-compact-serial/1383672025062576128 Apr 18 07:00:30.724236 ip-10-0-255-155 hyperkube[1464]: I0418 07:00:30.724202 1464 kubelet_pods.go:1285] "Killing unwanted pod" podName="prometheus-o perator-58474f67d6-h4tg2" Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: E0418 07:00:30.724640 1464 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: goroutine 20270 [running]: Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.logPanic(0x4201880, 0x75d86e0) Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: /builddir/build/BUILD/openshift-4.8.0/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0x95 Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0) Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: /builddir/build/BUILD/openshift-4.8.0/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x86 Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: panic(0x4201880, 0x75d86e0) Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: /usr/lib/golang/src/runtime/panic.go:965 +0x1b9 Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: k8s.io/kubernetes/pkg/kubelet/kuberuntime.(*kubeGenericRuntimeManager).killContainersWithSyncResult.func1(0xc000b82df0, 0xc000dbc000, 0x0, 0x0, 0xc002d9f140, 0xc004be53b0) Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: /builddir/build/BUILD/openshift-4.8.0/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/kuberuntime/kuberuntime_container.go:697 +0x33a Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: created by k8s.io/kubernetes/pkg/kubelet/kuberuntime.(*kubeGenericRuntimeManager).killContainersWithSyncResult Apr 18 07:00:30.724668 ip-10-0-255-155 hyperkube[1464]: /builddir/build/BUILD/openshift-4.8.0/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/kuberuntime/kuberuntime_container.go:690 +0x105
*** Bug 1951167 has been marked as a duplicate of this bug. ***
I checked the panic log of last few days from 4.8 ci job (https://search.ci.openshift.org/), didn't find any node's hyperkube panic related with "killContainers". verified!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438