Bug 1777930

Summary:	can't rsh to pod if dc not in latest version
Product:	OpenShift Container Platform	Reporter:	Samuel <smoro>
Component:	oc	Assignee:	Mike Dame <mdame>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.z	CC:	aos-bugs, jokerman, maszulik, mfojtik
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:17:52 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 Samuel 2019-11-28 17:36:25 UTC

Description of problem:

I can not rsh to a deploymentconfig, when its last rollout failed:

$ oc rsh dc/admin-demo
error: timed out waiting for the condition
$ oc get pods
NAME                              READY   STATUS      RESTARTS   AGE
admin-demo-10-deploy              0/1     Completed   0          5h47m
admin-demo-11-deploy              0/1     OOMKilled   0          4h41m
admin-demo-11-mvdg4               1/1     Running     0          4h40m
admin-demo-12-deploy              0/1     OOMKilled   0          54m
admin-demo-8-deploy               0/1     OOMKilled   0          6h23m
admin-demo-9-deploy               0/1     OOMKilled   0          6h6m
$ oc rsh admin-demo-11-mvdg4
sh-4.2$ exit
exit
$


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

$ oc version
Client Version: openshift-clients-4.2.0-201910041700
Server Version: 4.2.4

How reproducible:

Unsure

Steps to Reproduce:
1. rollout new image to deployment, image fails to start
2. rsh to deployment

Actual results:

rsh fails

Expected results:

rsh should send me to whichever pod is running

Additional info:

Comment 1 Maciej Szulik 2020-02-20 17:50:05 UTC

I think this might have been fixed with the latest changes to rsh, moving to qa.

Comment 5 zhou ying 2020-02-21 05:16:50 UTC

Can't reproduce the issue now:

[zhouying@dhcp-140-138 test-bugs]$ oc version -o yaml 
clientVersion:
  buildDate: "2020-02-20T23:06:08Z"
  compiler: gc
  gitCommit: 60a73ae84675e83931fcbb4fd5140972df06f594
  gitTreeState: clean
  gitVersion: v4.4.0
  goVersion: go1.13.4
  major: ""
  minor: ""
  platform: linux/amd64


[zhouying@dhcp-140-138 test-bugs]$ oc get po 
NAME                READY   STATUS             RESTARTS   AGE
hooks-1-56v25       1/1     Running            0          13s
hooks-1-deploy      0/1     Completed          0          18m
hooks-1-hook-mid    0/1     Completed          0          18m
hooks-1-hook-post   0/1     Completed          0          17m
hooks-1-hook-pre    0/1     Completed          0          18m
hooks-2-deploy      0/1     DeadlineExceeded   0          57s
hooks-2-hook-mid    0/1     Completed          0          14s
hooks-2-hook-pre    0/1     Completed          0          54s
[zhouying@dhcp-140-138 test-bugs]$ oc rsh po/hooks-1-56v25
sh-4.2$ date
Fri Feb 21 05:15:26 UTC 2020

Comment 7 errata-xmlrpc 2020-05-04 11:17:52 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