Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1750610

Summary: openshift-kube-apiserver pod spec is wrong for the loglevel flag -v
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: kube-apiserverAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, jokerman, mfojtik, mmccomas, yinzhou
Target Milestone: ---Keywords: Regression
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1679898 Environment:
Last Closed: 2019-10-16 06:40:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Xingxing Xia 2019-09-10 04:21:23 UTC 
+++ 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:
...
Comment 2 zhou ying 2019-09-18 03:39:11 UTC 
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
Comment 3 errata-xmlrpc 2019-10-16 06:40:50 UTC 
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