The termination lock file /var/log/kube-apiserver/.terminating is missing sometimes although it should exist.
Verified with OCP 4.6.0-0.nightly-2020-09-14-221526 according to the PR https://github.com/openshift/kubernetes/pull/332, $ oc debug node/<master node> sh-4.4# chroot /host sh-4.4# cd /var/log/kube-apiserver sh-4.4# ls -al total 163904 drwx------. 2 root root 66 Sep 15 02:11 . drwxr-xr-x. 16 root root 277 Sep 15 01:47 .. -rw-r--r--. 1 root root 0 Sep 15 02:11 .terminating -rw-r--r--. 1 root root 103913009 Sep 15 02:40 audit.log -rw-r--r--. 1 root root 4056358 Sep 15 02:11 termination.log sh-4.4# ps -ef |grep ' kube-apiserver ' root 58146 56671 63 02:56 ? 00:00:58 kube-apiserver --openshift-config=/etc/kubernetes/static-pod-resources/configmaps/config/config.yaml --advertise-address=xx.0.xxx.91 -v=2 root 60009 38559 0 02:58 ? 00:00:00 grep kube-apiserver sh-4.4# kill -9 58146 sh-4.4# tail -2 termination.log I0915 02:55:55.964944 19 httplog.go:94] "HTTP" verb="GET" URI="/readyz" latency="3.013261ms" userAgent="ELB-HealthChecker/2.0" srcIP="xx.0.xx.205:32323" resp=0 Previous pod kube-apiserver-ip-xx-0-xxx-91.us-east-2.compute.internal started at 2020-09-15 02:11:58.348874584 +0000 UTC did not terminate gracefully --- From above the logs, the expected log was displayed, so move the bug verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196