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

Bug 1474408

Summary:	After Docker restart pod is failing with 'Transport endpoint is not connected'
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	Storage	Assignee:	Bradley Childs <bchilds>
Status:	CLOSED DUPLICATE	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	aos-bugs, aos-storage-staff, eparis
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:	2017-07-25 13:28:24 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 Vladislav Walek 2017-07-24 14:25:17 UTC

Description of problem:

With gluster persistent volume. 
If the docker daemon service is restarted, then the pod is failing with error "Transport endpoint is not connected".
The get it fixed, the deployment must be redeployed and new pods are created, then the volume is reconnected.

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.4

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 3 Eric Paris 2017-07-25 13:28:24 UTC


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