Bug 1779535 - oc rollout restart is missing in oc
Summary: oc rollout restart is missing in oc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Tomáš Nožička
QA Contact: zhou ying
URL:
Whiteboard:
Depends On: 1779534
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 07:17 UTC by Tomáš Nožička
Modified: 2020-01-23 11:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1779534
Environment:
Last Closed: 2020-01-23 11:17:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift oc pull 199 0 'None' closed [release-4.3] Bug 1779535: Wire in `oc rollout restart` from kubectl 2021-02-16 03:29:08 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:18:04 UTC

Description Tomáš Nožička 2019-12-04 07:17:59 UTC
+++ This bug was initially created as a clone of Bug #1779534 +++

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-06 02:52:57 UTC
Confirmed with oc version : 
[root@dhcp-140-138 ~]# oc version -o yaml
clientVersion:
  buildDate: "2019-12-05T04:26:47Z"
  compiler: gc
  gitCommit: 3fa38ed2761a75d4c648acfc8ac14df930219ed5
  gitTreeState: clean
  gitVersion: v4.3.0
  goVersion: go1.12.12


The issue has fixed:

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


[root@dhcp-140-138 ~]# oc rollout restart daemonset.apps/fluentd-elasticsearch  -n kube-system
daemonset.apps/fluentd-elasticsearch restarted

Comment 4 errata-xmlrpc 2020-01-23 11:17:47 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:0062


Note You need to log in before you can comment on or make changes to this bug.