-
Bug
-
Resolution: Unresolved
-
Major
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
Approved
-
MCO Sprint 277
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-60120. The following is the description of the original issue:
—
Description of problem:
Panic seen in below 4.20 CI job for MCO pod with this error
panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x21e5aef]
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Steps to Reproduce:
Logs related to panic can be seen here
gcp- https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-gcp-ipi-longduration-tp-mco-p3-f7/1952019905905692672/artifacts/gcp-ipi-longduration-tp-mco-p3-f7/gather-extra/artifacts/pods/openshift-machine-config-operator_machine-config-operator-675b5c99c4-njlx9_machine-config-operator_previous.log
vsphere- https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-vsphere-upi-zones-f7-longrun-mco-tp-p1/1952136183110701056/artifacts/vsphere-upi-zones-f7-longrun-mco-tp-p1/gather-extra/artifacts/pods/openshift-machine-config-operator_machine-config-operator-675b5c99c4-n8fp2_machine-config-operator_previous.log
Actual results:
Expected results:
No panic expected
Additional info:
- blocks
-
TRT-2302 Select 4.20 RC.3 from Nightly
-
- Closed
-
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
