Bug 1924135

Summary: Under sufficient load, CRI-O may segfault
Product: OpenShift Container Platform Reporter: Peter Hunt <pehunt>
Component: NodeAssignee: Peter Hunt <pehunt>
Node sub component: CRI-O QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: aos-bugs, mpatel, nelluri, smilner
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: aos-scalability-47
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:57:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1922292    

Description Peter Hunt 2021-02-02 16:59:31 UTC
Description of problem:
If CRI-O is taking a long time to fulfill requests, it may get into a situation where it segfaults.

see
http://dell-r510-01.perf.lab.eng.rdu2.redhat.com/large-scale/4.7-sdn-kube-1.20/pod-density/worker:ip-10-0-248-118.us-west-2.compute.internal/crio.log

In addition to being a bad thing, it also can cause nodes to become not ready, as it makes an already resource intense situation even worse.

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

How reproducible:
The situation is hard to get into, but pretty reproducable

Steps to Reproduce:
1. Setup a node to be sufficiently under load
2. Notice a segfault in cri-o

Actual results:
cri-o segfaults

Expected results:
cri-o does not segfault

Additional info:

Comment 1 Peter Hunt 2021-02-02 17:01:09 UTC
Fixed in 4.7 version of the attached PR

Comment 6 Peter Hunt 2021-02-03 16:55:16 UTC
    4.7 version merged

Comment 14 errata-xmlrpc 2021-02-24 15:57:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633