-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.16.z
-
None
-
False
-
Description of problem:
A new release (4.16.31) was promoted earlier today and during the regular processing of the release, by the release-controller, we observed a panic in the APIServer.
Version-Release number of selected component (if applicable):
4.16.30
How reproducible:
I have been able to reproduce the panic multiple times via direct oc commands.
Steps to Reproduce:
1. Run the following command: oc -n test adm release mirror registry.ci.openshift.org/ocp-multi/release-multi:4.16.31 --to-image-stream=4.16.31 --keep-manifest-list=true
Actual results:
Error from server (InternalError): an error on the server ("This request caused apiserver to panic. Look in the logs for details.") has prevented the request from succeeding (post imagestreamimports.image.openshift.io)
Expected results:
The imagestream gets mirrored successfully
Additional info:
Corresponding APIServer entry:
E0116 14:23:46.496825 1 runtime.go:77] Observed a panic: runtime error: invalid memory address or nil pointer dereference
panic({0x4989c40?, 0x74a2190?})
runtime/panic.go:914 +0x21f
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x4743b40?, 0xc24d681410})
panic({0x4743b40?, 0xc24d681410?})
runtime/panic.go:914 +0x21f
panic({0x4743b40?, 0xc24d681410?})
runtime/panic.go:914 +0x21f
k8s.io/apiserver/pkg/server.DefaultBuildHandlerChain.WithPanicRecovery.withPanicRecovery.func32({0x5613480?, 0xc2b2d20000?}, 0xc3056da780?)
E0116 14:23:46.496857 1 wrap.go:58] "apiserver panic'd" method="POST" URI="/apis/image.openshift.io/v1/namespaces/ocp-multi/imagestreamimports?timeout=3m0s" auditID="c0de29e8-e3a0-4853-8497-328c298e4389"
- duplicates
-
-
- Verified
-