Bug 1925262

Summary:	apiserver getting 2 SIGTERM signals which was immediately making it exit code 1
Product:	OpenShift Container Platform	Reporter:	Harshal Patil <harpatil>
Component:	Node	Assignee:	Mrunal Patel <mpatel>
Node sub component:	CRI-O	QA Contact:	Weinan Liu <weinliu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	high	CC:	aos-bugs, mpatel, nagrawal, pehunt, weinliu
Version:	4.7
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:58:18 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:

Description Harshal Patil 2021-02-04 17:31:11 UTC

Creating this bug to track the issue of container process getting 2 SIGTERM signals and exiting with 1 immediately that we discovered as a part of https://bugzilla.redhat.com/show_bug.cgi?id=1882750#c57

Comment 1 Mrunal Patel 2021-02-04 17:47:38 UTC

https://github.com/cri-o/cri-o/pull/4539

Comment 2 Peter Hunt 2021-02-05 14:47:54 UTC

PR merged

Comment 7 errata-xmlrpc 2021-02-24 15:58:18 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