Bug 2098230 - Router process ignores shutdown signal while starting up
Summary: Router process ignores shutdown signal while starting up
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Grant Spence
QA Contact: Shudi Li
Depends On: 2076297
TreeView+ depends on / blocked
Reported: 2022-06-17 16:10 UTC by OpenShift BugZilla Robot
Modified: 2022-10-12 08:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The openshift-router process was ignoring the SIGTERM shutdown signal for a brief moment as it was starting. Consequence: If a SIGTERM was sent while the router process was starting up, it would ignore the signal. This means the container would ignore a kubernetes shutdown request resulting in the container taking 1 hour to shutdown (terminationGracePeriodSeconds). Fix: Propagate the SIGTERM handler in GO code to the cache initialization function. Result: The router now responds to SIGTERM signals during it initialization.
Clone Of:
Last Closed: 2022-10-12 08:51:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift router pull 406 0 None Merged [release-4.10] Bug 2098230: Fix gap in router's handling of graceful shutdowns. 2022-09-28 19:21:01 UTC
Red Hat Product Errata RHSA-2022:6805 0 None None None 2022-10-12 08:51:49 UTC

Comment 5 errata-xmlrpc 2022-10-12 08:51:28 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 (Important: OpenShift Container Platform 4.10.36 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.


Note You need to log in before you can comment on or make changes to this bug.