Bug 1809028

Summary:	oc wait -h shows 'kubectl' examples
Product:	OpenShift Container Platform	Reporter:	Eduardo Minguez <eminguez>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jokerman, mfojtik
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-04 18:03:03 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:
Embargoed:

Description Eduardo Minguez 2020-03-02 09:49:00 UTC

Description of problem: oc wait -h shows 'kubectl' instead 'oc'


Version-Release number of selected component (if applicable):
$ oc version
Client Version: 4.4.0-0.nightly-2020-02-28-000349


How reproducible:
$ oc wait -h
...
Usage:
  oc wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)]) [--for=delete|--for
condition=available] [flags]

Examples:
  # Wait for the pod "busybox1" to contain the status condition of type "Ready".
  kubectl wait --for=condition=Ready pod/busybox1
  
  # Wait for the pod "busybox1" to be deleted, with a timeout of 60s, after having issued the "delete" command.
  kubectl delete pod/busybox1
  kubectl wait --for=delete pod/busybox1 --timeout=60s

Steps to Reproduce:
1. Download latest `oc` binary from https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/latest/
2. Run `oc wait -h`

Actual results:
The examples talk about kubectl

Expected results:
The examples should use 'oc' instead.


Additional info:

Comment 4 zhou ying 2020-03-23 00:36:38 UTC

the issue has fixed:
[root@dhcp-140-138 ~]#  oc version 
Client Version: 4.5.0-202003220416-abb27a9
Unable to connect to the server: dial tcp: lookup api.ocp-edge-cluster.qe.lab.redhat.com on 10.72.17.5:53: no such host
[root@dhcp-140-138 ~]#  oc version  -o yaml 
clientVersion:
  buildDate: "2020-03-22T04:22:13Z"
  compiler: gc
  gitCommit: abb27a9c2991a316982aa712399d50e67589c81d
  gitTreeState: clean
  gitVersion: 4.5.0-202003220416-abb27a9
  goVersion: go1.13.4
  major: ""
  minor: ""
  platform: linux/amd64



[root@dhcp-140-138 ~]# oc wait -h
Experimental: Wait for a specific condition on one or many resources.

 The command takes multiple resources and waits until the specified condition is seen in the Status field of every given
resource.

 Alternatively, the command can wait for the given set of resources to be deleted by providing the "delete" keyword as
the value to the --for flag.

 A successful message will be printed to stdout indicating when the specified condition has been met. One can use -o
option to change to output destination.

Usage:
  oc wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)]) [--for=delete|--for
condition=available] [flags]

Examples:
  # Wait for the pod "busybox1" to contain the status condition of type "Ready".
  oc wait --for=condition=Ready pod/busybox1
  
  # Wait for the pod "busybox1" to be deleted, with a timeout of 60s, after having issued the "delete" command.
  oc delete pod/busybox1
  oc wait --for=delete pod/busybox1 --timeout=60s

Comment 6 errata-xmlrpc 2020-08-04 18:03:03 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 (OpenShift Container Platform 4.5 image release 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-2020:2409