Bug 1294797 - "Transport endpoint not connected" in heal info though hot tier bricks are up
Summary: "Transport endpoint not connected" in heal info though hot tier bricks are up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On: 1277944 1294794
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-30 11:32 UTC by Avra Sengupta
Modified: 2016-04-19 07:52 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.7.7
Clone Of: 1294794
Environment:
Last Closed: 2016-04-19 07:52:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-12-30 11:34:23 UTC 
REVIEW: http://review.gluster.org/13119 (snapd: Do not persist snapd port) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)
Comment 2 Vijay Bellur 2016-01-04 05:53:39 UTC 
REVIEW: http://review.gluster.org/13119 (snapd: Do not persist snapd port) posted (#2) for review on release-3.7 by Avra Sengupta (asengupt)
Comment 3 Vijay Bellur 2016-01-23 05:21:29 UTC 
REVIEW: http://review.gluster.org/13119 (snapd: Do not persist snapd port) posted (#3) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
Comment 4 Vijay Bellur 2016-01-27 02:46:55 UTC 
REVIEW: http://review.gluster.org/13119 (snapd: Do not persist snapd port) posted (#4) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
Comment 5 Vijay Bellur 2016-01-31 02:27:07 UTC 
COMMIT: http://review.gluster.org/13119 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit c4d7c50a7354ad92e76ea72fccc86e0732e75c49
Author: Avra Sengupta <asengupt>
Date:   Wed Dec 30 16:37:05 2015 +0530

    snapd: Do not persist snapd port
    
        Backport of http://review.gluster.org/#/c/13118/
    
    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: 1294797
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/13119
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
Comment 6 Kaushal 2016-04-19 07:52:20 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.7.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Note You need to log in before you can comment on or make changes to this bug.