Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1348802

Summary:	[docker1.10]'oc rsh' and 'oc exec' commands could not work against ose-3.1 with docker-1.10
Product:	OpenShift Container Platform	Reporter:	Wei Sun <wsun>
Component:	oc	Assignee:	Fabiano Franz <ffranz>
Status:	CLOSED WONTFIX	QA Contact:	Xingxing Xia <xxia>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	aos-bugs, bleanhar, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
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:	2016-12-02 21:41:35 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 Wei Sun 2016-06-22 06:33:51 UTC

Description of problem:
In ose-3.1 with docker-1.10 env,use 'oc rsh' or 'oc exec' commands,the commands could not work and hang there.

Version-Release number of selected component (if applicable):
openshift v3.1.1.6-64-g80b61da
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2
docker-1.10.3-44.el7.x86_64
docker-common-1.10.3-44.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Create a pod
2.oc rsh or oc exec
3.

Actual results:
`oc rsh` and `oc exec` commands could not work,and hang there

Expected results:
The commands could work well

Additional info:
The command work well against ose-3.1 with docker-1.8(docker-1.8.2-10.el7.x86_64)

Comment 1 Brenton Leanhardt 2016-06-22 08:20:32 UTC

Lowering the severity simply because we haven't decided if this is even
supported.

Comment 2 Fabiano Franz 2016-12-02 21:22:18 UTC

Brenton, is this still relevant?

Comment 3 Brenton Leanhardt 2016-12-02 21:41:35 UTC

OCP 3.1 only supports Docker 1.8.2:

https://docs.openshift.com/enterprise/3.1/install_config/install/prerequisites.html

I suspect this bug came as a request from QE to see what breaks if we tried with Docker 1.10.  Closing this.