-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.13, 4.14
-
None
-
Moderate
-
No
-
uShift Sprint 236, uShift Sprint 237
-
2
-
False
-
Description of problem:
killing microshift-etcd with a normally non-fatal signal like SIGHUP or SIGINT the process becomes defunct requiring a microshift restart. Normally systemd managed processes automatically restart on signals like this.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Always
Steps to Reproduce:
1. Get the pid of microshift-etcd and kill -1 on it
Actual results:
1. ps -ef on microshift-etcd shows it as defunct and still parented by microshift 2. Nobody home on port 2379 and the cluster is unresponsive until microshift is restarted.
Expected results:
Cleanly handle signals and restart
Additional info:
- links to
-
RHSA-2023:5008 OpenShift Container Platform 4.14.z security update