Bug 2098230
| Summary: | Router process ignores shutdown signal while starting up | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Networking | Assignee: | Grant Spence <gspence> |
| Networking sub component: | router | QA Contact: | Shudi Li <shudili> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, hongli, mmasters, wking |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-12 08:51:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2076297 | ||
| Bug Blocks: | |||
|
Comment 5
errata-xmlrpc
2022-10-12 08:51:28 UTC
|