Bug 1649727

Summary:	Some pods in running state but not accessible via rsh or exec
Product:	OpenShift Container Platform	Reporter:	Madhusudan Upadhyay <maupadhy>
Component:	Node	Assignee:	Robert Krawitz <rkrawitz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Weinan Liu <weinliu>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, jhou, jokerman, lmeyer, mmccomas, pdwyer, rkrawitz, sauchter, sjenning
Target Milestone:	---
Target Release:	3.11.z
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:	2018-12-14 14:39:53 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 Madhusudan Upadhyay 2018-11-14 11:44:54 UTC

Description of problem:

- Cannot rsh the pod with the following error:

[root@customer ~]# oc rsh <pod_name>
error: unable to upgrade connection: error dialing backend: dial tcp 127.0.0.1:xxxxx: connect: cannot assign requested address

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

- error: unable to upgrade connection: error dialing backend: dial tcp 127.0.0.1:xxxxx: connect: cannot assign requested address


Expected results:

- Successful rsh into the pod


Additional info:

- The bug is being tracked in kubernetes 1.11:
  [+] https://github.com/kubernetes/kubernetes/issues/67659

1. Attached to the case is the sos report of the node
2. Appended is the output of  oc rsh --loglevel=8 <pod_name>

Comment 1 Seth Jennings 2018-11-14 15:13:50 UTC

Seems to be fixed by https://github.com/kubernetes/kubernetes/pull/67288

Looking to backport.

Comment 5 Madhusudan Upadhyay 2018-11-15 06:14:53 UTC

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

Comment 18 Jianwei Hou 2018-12-14 06:10:49 UTC

The advisory shipped v3.11.51. I've verified this is fixed in v3.11.51.

Comment 19 Luke Meyer 2018-12-14 14:39:53 UTC

Fix shipped with https://access.redhat.com/errata/RHBA-2018:3743 before being verified.