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:
Fixed in 4.7 version of the attached PR
4.7 version merged
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