Bug 1927500

Summary: API server exits non-zero on 2 SIGTERM signals
Product: OpenShift Container Platform Reporter: Ryan Phillips <rphillips>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Mike Fiedler <mifiedle>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.7CC: aos-bugs, jluhrsen, kewang, mfojtik, mifiedle, mpatel, sttts, wking, xxia
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1926484 Environment:
Last Closed: 2021-02-24 15:58:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1926484    
Bug Blocks:    

Description Ryan Phillips 2021-02-10 21:00:08 UTC
+++ This bug was initially created as a clone of Bug #1926484 +++

Description of problem:
API server exits immediately if it received 2 SIGTERMs.
 We use systemd scopes for containers in OpenShift today and they don't support mixed mode (See https://bugzilla.redhat.com/show_bug.cgi?id=1925623). So, to make sure that the API server can gracefully shutdown, we need to make it resilient to multiple SIGTERMs during reboot/shutdown.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Ryan Phillips 2021-02-10 21:01:16 UTC
Placeholder for the 4.7 cherry pick... https://github.com/openshift/kubernetes/pull/558 is pending merge to master.

Comment 3 Mike Fiedler 2021-02-12 15:32:25 UTC
Verified on 4.7.0-0.nightly-2021-02-12-013204

Second SIGTERM to kube-apiserver PID does not interrupt shutdown.

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