Bug 1924135 - Under sufficient load, CRI-O may segfault
Summary: Under sufficient load, CRI-O may segfault
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Peter Hunt
QA Contact: Sunil Choudhary
Whiteboard: aos-scalability-47
Depends On:
Blocks: 1922292
TreeView+ depends on / blocked
Reported: 2021-02-02 16:59 UTC by Peter Hunt
Modified: 2021-02-24 15:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:57:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 4530 0 None open ResourceStore: fix segfault and update tests 2021-02-09 06:28:01 UTC
Github cri-o cri-o pull 4535 0 None closed [1.20] ResourceStore: fix segfault and update tests 2021-02-09 06:28:02 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:58:06 UTC

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.


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):

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.


Note You need to log in before you can comment on or make changes to this bug.