Bug 1780447

Summary:	Need update info for `oc rollout restart`
Product:	OpenShift Container Platform	Reporter:	zhou ying <yinzhou>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.0	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-07-13 17:12:38 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 zhou ying 2019-12-06 03:24:18 UTC

Description of problem:
Need update info for `oc rollout restart`

Version-Release number of selected component (if applicable):
Client Version: v4.3.0
Server Version: 4.3.0-0.nightly-2019-12-05-213858

How reproducible:
always

Steps to Reproduce:
1. `oc rollout -h`
2. oc rollout restart -h
...
  kubectl rollout restart deployment/nginx
  # Restart a daemonset
  kubectl rollout restart daemonset/abc

Actual results:
1. Show: 
Available Commands:
  cancel      cancel the in-progress deployment
  history     View rollout history
  latest      Start a new rollout for a deployment config with the latest state from its triggers
  pause       Mark the provided resource as paused
  restart     Restart a resource
....

2. show kubectl instead of oc


Expected results:
1. Indicate only deployment and daemonset resources support restart command.
2 show oc


Additional info:

Comment 1 Maciej Szulik 2019-12-11 13:17:09 UTC

This will be fixed in https://github.com/openshift/oc/pull/132

Comment 7 Maciej Szulik 2020-05-04 10:21:24 UTC

Automation failed on this one, moving manually to on-qa.

Comment 8 zhou ying 2020-05-06 02:56:36 UTC

with the latest oc client :
[root@dhcp-140-138 ~]# oc version -o yaml 
clientVersion:
  buildDate: "2020-05-02T15:23:53Z"
  compiler: gc
  gitCommit: 29e9a330f0ab0eed17b5ba6a8cc198ccc4332567
  gitTreeState: clean
  gitVersion: 4.5.0-202005021517-29e9a33
  goVersion: go1.13.4
  major: ""
  minor: ""
  platform: linux/amd64

we still could see the 'kubectl' but not the oc in the example:
[root@dhcp-140-138 ~]# oc rollout restart -h
Restart a resource.

     Resource will be rollout restarted.

Usage:
  oc rollout restart RESOURCE [flags]

Examples:
  # Restart a deployment
  kubectl rollout restart deployment/nginx
  
  # Restart a daemonset
  kubectl rollout restart daemonset/abc

Comment 11 zhou ying 2020-05-15 05:48:35 UTC

[root@dhcp-140-138 roottest]# oc version -o yaml 
clientVersion:
  buildDate: "2020-05-14T09:22:10Z"
  compiler: gc
  gitCommit: 95473305f0eba6b37cec9246244ee7c375897d9f
  gitTreeState: clean
  gitVersion: 4.5.0-202005140917-9547330
  goVersion: go1.13.4
  major: ""
  minor: ""
  platform: linux/amd64


[root@dhcp-140-138 roottest]# oc rollout restart -h
Restart a resource.

 Resource will be rollout restarted.

Usage:
  oc rollout restart RESOURCE [flags]

Examples:
  # Restart a deployment
  oc rollout restart deployment/nginx
  
  # Restart a daemonset
  oc rollout restart daemonset/abc

Comment 13 errata-xmlrpc 2020-07-13 17:12:38 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-2020:2409