Bug 1831533

Summary: stop printing usage help when the server commands
Product: OpenShift Container Platform Reporter: Lukasz Szaszkiewicz <lszaszki>
Component: kube-apiserverAssignee: Lukasz Szaszkiewicz <lszaszki>
Status: CLOSED ERRATA QA Contact: Ke Wang <kewang>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, mfojtik, wking, xxia
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1838195 (view as bug list) Environment:
Last Closed: 2020-07-13 17:34:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1838195, 1838197, 1838198, 1838199    

Description Lukasz Szaszkiewicz 2020-05-05 07:29:39 UTC
move https://github.com/kubernetes/kubernetes/pull/90297 into origin so that help is not printed when kube-apiserver fails with a non usage based error

Comment 3 Ke Wang 2020-05-07 07:45:51 UTC
Verified with OCP build 4.5.0-0.nightly-2020-05-06-003431,

- On 4.4 OCP without fix ENV, get the related errors
2020-05-06T15:10:17.009079506+00:00 stderr F Usage:
2020-05-06T15:10:17.009079506+00:00 stderr F   kube-apiserver [flags]
2020-05-06T15:10:17.009079506+00:00 stderr F
2020-05-06T15:10:17.009079506+00:00 stderr F Generic flags:
2020-05-06T15:10:17.009079506+00:00 stderr F

- In one terminal, enter into master 
$ master=$(oc get nodes | grep master | head -1 | cut -d " " -f1)
$ oc debug node/$master
sh-4.2# chroot /host
Try incorrect parameter to endpoint,
sh-4.4#  curl -k --silent --show-error https://localhost:6443/readyz1

$ cd /var/log/pods

$ grep -nr -i 'usage' openshift-*

No results found.

So the bug was fixed, move the bug verified.

Comment 4 David Eads 2020-05-20 14:54:04 UTC
*** Bug 1822417 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2020-07-13 17:34:48 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.