-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.18.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
Critical
-
None
-
None
-
Proposed
-
MCO Sprint 267, MCO Sprint 268
-
2
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-45860. 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-vsphere-ovn-upi-serial/1861922894817267712
Undiagnosed panic detected in pod { pods/openshift-machine-config-operator_machine-config-daemon-4mzxf_machine-config-daemon_previous.log.gz:E1128 00:28:30.700325 4480 panic.go:261] "Observed a panic" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<}
- clones
-
OCPBUGS-46011 VSphere MCO Panic
-
- Closed
-
- is blocked by
-
OCPBUGS-46011 VSphere MCO Panic
-
- Closed
-
- is related to
-
OCPBUGS-48201 Panic seen in CI job for MCD pod
-
- Closed
-
- relates to
-
OCPBUGS-48201 Panic seen in CI job for MCD pod
-
- Closed
-
- links to
-
RHSA-2025:3059 OpenShift Container Platform 4.17.22 bug fix and security update
(1 links to)