Bug 1779534

Summary:	oc rollout restart is missing in oc
Product:	OpenShift Container Platform	Reporter:	Tomáš Nožička <tnozicka>
Component:	oc	Assignee:	Tomáš Nožička <tnozicka>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	aos-bugs, jokerman, mfojtik
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The command wasn't wired. Consequence: The command was missing. Fix: Wired the upstream command. Result: The command is now available in oc.	Story Points:	---
Clone Of:
Clones:	1779535 (view as bug list)		Environment:
Last Closed:	2020-05-13 21:53:54 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:
Bug Depends On:
Bug Blocks:	1779535

Description Tomáš Nožička 2019-12-04 07:16:17 UTC

Description of problem:

`rollout restart` command is missing in oc


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 zhou ying 2019-12-16 02:47:52 UTC

Confirmed with latest version , the issue has fixed:
[root@dhcp-140-138 ~]# oc version -o yaml 
clientVersion:
  buildDate: "2019-12-13T16:45:38Z"
  compiler: gc
  gitCommit: 60ccef2e295e103fa6bd01b9ae5de9061386b948
  gitTreeState: clean
  gitVersion: v4.4.0
  goVersion: go1.12.12
  major: ""
  minor: ""
  platform: linux/amd64

[root@dhcp-140-138 ~]# oc rollout -h
Start a new rollout, view its status or history, rollback to a previous revision of your app

......
  restart     Restart a resource


[root@dhcp-140-138 ~]# oc rollout restart daemonset.apps/apiserver -n openshift-apiserver
daemonset.apps/apiserver restarted

Comment 4 errata-xmlrpc 2020-05-13 21:53:54 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:0581