Bug 1801292

Summary:	oc rsh doesn't take a -f
Product:	OpenShift Container Platform	Reporter:	David Eads <deads>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	aos-bugs, jokerman, maszulik, 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:14:44 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 David Eads 2020-02-10 15:04:44 UTC

[deads@deads-02 cluster-etcd-operator]$ oc rsh -f ~/Downloads/debug-pod.yaml 
Error: unknown shorthand flag: 'f' in -f


this prevents creating a pod manifest and rsh into it immediately.  the kubectl standard is to take a -f and harvest the namespace and name from it.

Comment 1 Maciej Szulik 2020-02-24 13:38:13 UTC

The upstream part is in https://github.com/kubernetes/kubernetes/pull/88460
we'll get it in the next release.

Comment 2 Maciej Szulik 2020-02-26 19:38:17 UTC

*** Bug 1707833 has been marked as a duplicate of this bug. ***

Comment 3 Maciej Szulik 2020-05-20 08:27:33 UTC

PRs in the queue.

Comment 6 zhou ying 2020-05-27 03:27:32 UTC

[zhouying@dhcp-140-138 ~]$ oc version 
Client Version: 4.5.0-202005270117-384535d
Kubernetes Version: v1.18.2+9835af5


[zhouying@dhcp-140-138 ~]$ oc rsh -f /tmp/hellopod.yaml  cat /etc/resolv.conf
search zhouyrsh.svc.cluster.local svc.cluster.local cluster.local c.openshift-qe.internal google.internal
nameserver 172.30.0.10
options ndots:5

Comment 8 errata-xmlrpc 2020-07-13 17:14:44 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