Bug 2052125 - [4.10] Crio appears to be coredumping in some scenarios
Summary: [4.10] Crio appears to be coredumping in some scenarios
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Peter Hunt
QA Contact: pmali
URL:
Whiteboard:
Depends On: 2050882
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-08 18:32 UTC by Peter Hunt
Modified: 2022-03-10 16:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2050882
Environment:
Last Closed: 2022-03-10 16:43:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 5611 0 None Merged [release-1.23] deep copy List{PodSandbox,Container} structs 2022-02-09 15:54:28 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:44:04 UTC

Comment 2 Peter Hunt 2022-02-08 18:35:11 UTC 
cri-o segfaulting is bad, especially because this periodically happens. setting to blocker
Comment 8 errata-xmlrpc 2022-03-10 16:43:51 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.10.3 security 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-2022:0056
Note You need to log in before you can comment on or make changes to this bug.