-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.14.0
-
None
-
No
-
3
-
uShift Sprint 241
-
1
-
False
-
-
Release Note Not Required
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:
- blocks
-
OCPBUGS-18773 MicroShift's KAS and KCM are not shutting down
- Closed
- is cloned by
-
OCPBUGS-18773 MicroShift's KAS and KCM are not shutting down
- Closed
- is related to
-
OCPBUGS-14678 When stopping microshift.service, microshift-etcd shuts down independently of microshift and before kube-apiserver
- Closed
- links to
-
RHEA-2023:7200 Red Hat build of MicroShift 4.15.z bug fix and enhancement update