Bug 1306193

Summary:	cd to .snaps fails with "transport endpoint not connected" after force start of the volume.
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	asengupt, bugs, rjoseph, sraj, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1305849
Clones:	1309233 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:57:06 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:	1305849
Bug Blocks:	1309233

Comment 1 Vijay Bellur 2016-02-10 09:48:14 UTC

REVIEW: http://review.gluster.org/13420 (glusterd/snapshot : Remove stale pmap registry entry) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2016-02-17 08:52:51 UTC

COMMIT: http://review.gluster.org/13420 committed in master by Rajesh Joseph (rjoseph) 
------
commit bfe689d25ecde567a90135b47f31b89d7714aaf4
Author: Avra Sengupta <asengupt>
Date:   Wed Feb 10 15:02:48 2016 +0530

    glusterd/snapshot : Remove stale pmap registry entry
    
    Perform a pmap_registry_remove on a stale registry
    entry from the previous run of snapd, which makes the
    query callback always return the older port number.
    
    Change-Id: I7fc504d2b09d32a9c945ec2c33e0e092a0d186ec
    BUG: 1306193
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/13420
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Niels de Vos 2016-06-16 13:57:06 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