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

Bug 1294794

Summary:	"Transport endpoint not connected" in heal info though hot tier bricks are up
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, asrivast, bugs, byarlaga, pkarampu, sankarshan, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1277944
Clones:	1294797 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:52:41 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:
Bug Depends On:	1277944
Bug Blocks:	1294797

Comment 1 Avra Sengupta 2015-12-30 11:10:53 UTC

Currently snapd persists the port it uses
to sign-in with glusterd, without checking 
if that particular port is being used by any 
other process. As a result, it might erroneously
sign out any other process using the same port.

Hence forcing snapd to ignore the persisted port,
and using a new one while coming up.

Comment 2 Vijay Bellur 2015-12-30 11:33:08 UTC

REVIEW: http://review.gluster.org/13118 (snapd: Do not persist snapd port) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 3 Vijay Bellur 2016-01-04 05:53:28 UTC

REVIEW: http://review.gluster.org/13118 (snapd: Do not persist snapd port) posted (#2) for review on master by Avra Sengupta (asengupt)

Comment 4 Vijay Bellur 2016-02-01 06:00:54 UTC

REVIEW: http://review.gluster.org/13118 (snapd: Do not persist snapd port) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 5 Vijay Bellur 2016-02-01 11:02:32 UTC

COMMIT: http://review.gluster.org/13118 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 4267c14e1be513b6124ef0dca75029494844f711
Author: Avra Sengupta <asengupt>
Date:   Wed Dec 30 16:37:05 2015 +0530

    snapd: Do not persist snapd port
    
    Currently snapd persists the port it uses
    to sign-in with glusterd, without checking
    if that particular port is being used by any
    other process. As a result, it might erroneously
    sign out any other process using the same port.
    
    Hence forcing snapd to ignore the persisted port,
    and using a new one while coming up.
    
    Change-Id: Ibb9ec3762aac445f03d96e85660585be4ab27bcb
    BUG: 1294794
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/13118
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 6 Niels de Vos 2016-06-16 13:52:41 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user