1. Start openshift-router 2. Hit CTRL+C Actual: Process does not exit Expected: Process exits If I hit CTRL+C a second time the process exits. It looks like someone double registered a sig trap handler somewhere in CLI or in the server code. Marking high because this breaks process signal handling in at minimum the router.
Looks like it is a result of origin/pr/19063
(In reply to Clayton Coleman from comment #1) > Looks like it is a result of origin/pr/19063 I moved the handling of the signal closer to NewCommandStartNode() but that only works some of the time now (8/10 signal is delivered successfully). Investigating why that is because it was reliable before.
PR: https://github.com/openshift/ose/pull/1221
The revert PR: https://github.com/openshift/ose/pull/1238 until we go fix the issues highlighted in the PR description.
Upstream PR: https://github.com/kubernetes/kubernetes/pull/63859
OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift