Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.14.z
Component/s: Node / CRI-O
Labels:
None

Activity Type:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Moderate
Regression:
None
Architecture:

All
Deployment Environment:
Production

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

RH Private Keywords:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

crio process unexpectedly crashed and generated a core dump when stopping a container. The stack trace and journal logs from the node indicate a panic was triggered after a call to a chansend routine, with the logs reporting "panic: send on closed channel"

Version-Release number of selected component (if applicable):

OpenShift Container Platform: 4.14.37
rhel-coreos image: d8bfae1166e8556d3f4e83fb934fef8b41107afccb66f748cd0b6eab806031f3
crio version 1.27.8-6.rhaos4.14.git06fccaa.el9

How reproducible:

N/A

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

This appears to be similar to existing closed tickets for etcd:

https://issues.redhat.com/browse/OCPBUGS-27959 (Parent)
- https://issues.redhat.com/browse/OCPBUGS-30067 (OCP 4.14)

is related to

OCPBUGS-27959 Panic: send on closed channel

Closed

OCPBUGS-30067 [4.14] Panic: send on closed channel

Closed

Assignee:: Sabuj Maity

Reporter:: Paul Webster

Need Info From:: None

Contributors:: None

QA Contact:: Min Li

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2026/02/10 2:46 AM

Updated:: 2026/02/19 5:51 PM