+++ This bug was initially created as a clone of Bug #1679898 +++ In 4.2.0-0.nightly-2019-09-09-235057, same issue: Set kubeapiserver/cluster logLevel to TraceAll. Wait kas pods restart. Check log level in process. No -v=8 shown: oc rsh -n openshift-kube-apiserver kube-apiserver-ip-10-0-130-160.sa-east-1.compute.internal sh-4.2# ps -eF | grep apiserver root 1 0 19 401686 913600 2 03:56 ? 00:02:24 hyperkube kube-apiserver --openshift-config=/etc/kubernetes/static-pod-resources/configmaps/config/config.yaml oc get pod kube-apiserver-ip-10-0-130-160.sa-east-1.compute.internal -n openshift-kube-apiserver -o yaml spec: containers: - args: - | if [ -f /etc/kubernetes/static-pod-resources/kube-apiserver-certs/configmaps/trusted-ca-bundle/tls-ca-bundle.pem ]; then echo "Copying system trust bundle" cp -f /etc/kubernetes/static-pod-resources/kube-apiserver-certs/configmaps/trusted-ca-bundle/tls-ca-bundle.pem /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem fi exec hyperkube kube-apiserver --openshift-config=/etc/kubernetes/static-pod-resources/configmaps/config/config.yaml - -v=8 # <-- placed wrong command: - /bin/bash - -ec env: ...
Confirmed with payload: 4.2.0-0.nightly-2019-09-17-232025, the issue has fixed: [root@dhcp-140-138 ~]# oc rsh -n openshift-kube-apiserver kube-apiserver-ip-10-0-169-15.us-east-2.compute.internal Defaulting container name to kube-apiserver-7. Use 'oc describe pod/kube-apiserver-ip-10-0-169-15.us-east-2.compute.internal -n openshift-kube-apiserver' to see all of the containers in this pod. sh-4.2# ps -eF |grep apiserver root 1 0 57 331636 728228 1 03:36 ? 00:00:56 hyperkube kube-apiserver --openshift-config=/etc/kubernetes/static-pod-resources/configmaps/config/config.yaml -v=8 root 30 22 0 2276 848 3 03:38 pts/0 00:00:00 grep apiserver
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, 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-2019:2922