Bug 1925262 - apiserver getting 2 SIGTERM signals which was immediately making it exit code 1
Summary: apiserver getting 2 SIGTERM signals which was immediately making it exit code 1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 4.7.0
Assignee: Mrunal Patel
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-04 17:31 UTC by Harshal Patil
Modified: 2021-02-24 15:58 UTC (History)
5 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:58:31 UTC

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
Note You need to log in before you can comment on or make changes to this bug.