-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.14.0
-
None
-
No
-
uShift Sprint 241, uShift Sprint 242
-
2
-
False
-
-
Fixed a problem that prevented MicroShift from shutting down cleanly in some circumstances.
-
Bug Fix
This is a clone of issue OCPBUGS-18548. The following is the description of the original issue:
—
Description of problem:
Fixing OCPBUGS-14678 uncovered another issue: after fixing the shutdown order, it appears that KCM and KAS do not exit even though they get a cancellation signal (via context).
Version-Release number of selected component (if applicable):
https://github.com/openshift/microshift/pull/2287
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
All MicroShift components stop almost immediately, but KAS and KCM do not, so MicroShift uses its full "graceful shutdown timeout" (which is 60 second but Evgeny's change shortens that to 15s).
Expected results:
KAS and KCM shut down in timely manner and don't block MicroShift shutdown
Additional info:
- clones
-
OCPBUGS-18548 MicroShift's KAS and KCM are not shutting down
- Closed
- is blocked by
-
OCPBUGS-18548 MicroShift's KAS and KCM are not shutting down
- Closed
- links to
-
RHSA-2023:5008 OpenShift Container Platform 4.14.z security update