-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
This is a clone of issue OCPBUGS-48633. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45861. The following is the description of the original issue:
—
The following test is failing more than expected:
Undiagnosed panic detected in pod
See the sippy test details for additional context.
Observed in 4.18-e2e-telco5g-cnftests/1863644602574049280 and 4.18-e2e-telco5g/1863677472923455488
Undiagnosed panic detected in pod { pods/openshift-kube-apiserver_kube-apiserver-cnfdu3-master-1_kube-apiserver.log.gz:E1202 22:12:02.806740 12 audit.go:84] "Observed a panic" panic="context deadline exceeded" panicGoValue="context.deadlineExceededError{}" stacktrace=<}
Undiagnosed panic detected in pod { pods/openshift-kube-apiserver_kube-apiserver-cnfdu11-master-2_kube-apiserver.log.gz:E1202 22:11:42.359004 14 timeout.go:121] "Observed a panic" panic=<}
- blocks
-
OCPBUGS-49656 telco openshift-apiserver panic observed
- ASSIGNED
- clones
-
OCPBUGS-48633 telco openshift-apiserver panic observed
- Verified
- is blocked by
-
OCPBUGS-48633 telco openshift-apiserver panic observed
- Verified
- is cloned by
-
OCPBUGS-49656 telco openshift-apiserver panic observed
- ASSIGNED
- links to