Bug 1649728 - Some pods in running state but not accessible via rsh or exec
Summary: Some pods in running state but not accessible via rsh or exec
Keywords:
Status: CLOSED DUPLICATE of bug 1649727
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Seth Jennings
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-14 11:45 UTC by Madhusudan Upadhyay
Modified: 2018-11-15 06:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-15 06:14:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Madhusudan Upadhyay 2018-11-14 11:45:06 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 3 Madhusudan Upadhyay 2018-11-15 06:14:53 UTC

*** This bug has been marked as a duplicate of bug 1649727 ***


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