Bug 1474408 - After Docker restart pod is failing with 'Transport endpoint is not connected'
Summary: After Docker restart pod is failing with 'Transport endpoint is not connected'
Keywords:
Status: CLOSED DUPLICATE of bug 1424680
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bradley Childs
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 14:25 UTC by Vladislav Walek
Modified: 2017-07-25 13:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-25 13:28:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.