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

Bug 1427399

Summary:	[RFE] capture portmap details in glusterd's statedump
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1426948	Environment:
Last Closed:	2017-04-05 00:01:42 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:	1426948
Bug Blocks:	1426950

Description Atin Mukherjee 2017-02-28 05:58:03 UTC

+++ This bug was initially created as a clone of Bug #1426948 +++

Description of problem:

capture portmap details in glusterd's statedump. This would be quite useful while debugging stale ports issue.

Version-Release number of selected component (if applicable):
mainline

--- Additional comment from Worker Ant on 2017-02-26 12:38:01 EST ---

REVIEW: https://review.gluster.org/16764 (glusterd: add portmap details in glusterd statedump) posted (#1) for review on master by Atin Mukherjee (amukherj)

--- Additional comment from Worker Ant on 2017-02-27 08:47:57 EST ---

COMMIT: https://review.gluster.org/16764 committed in master by Atin Mukherjee (amukherj) 
------
commit dbdfe6c353060b7af7b4250c8d6c30ed0c35783c
Author: Atin Mukherjee <amukherj>
Date:   Sun Feb 26 23:00:21 2017 +0530

    glusterd: add portmap details in glusterd statedump
    
    glusterd statedump file doesn't have information on the ports and its
    associated brick details. This is quite problematic if any setup ends up
    with stale ports and the only way to find the issue out is to gdb into
    the process which is always not available. This patch attempts to fill
    in this gap.
    
    Change-Id: I26b4fe753d752366ddf865ca3eeae3b4d577d555
    BUG: 1426948
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: https://review.gluster.org/16764
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Prashanth Pai <ppai>

Comment 1 Worker Ant 2017-02-28 05:59:37 UTC

REVIEW: https://review.gluster.org/16779 (glusterd: add portmap details in glusterd statedump) posted (#1) for review on release-3.10 by Atin Mukherjee (amukherj)

Comment 2 Worker Ant 2017-03-03 15:13:09 UTC

COMMIT: https://review.gluster.org/16779 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 9b95b1e82fa722d92ef1259495fce386833e6f15
Author: Atin Mukherjee <amukherj>
Date:   Sun Feb 26 23:00:21 2017 +0530

    glusterd: add portmap details in glusterd statedump
    
    glusterd statedump file doesn't have information on the ports and its
    associated brick details. This is quite problematic if any setup ends up
    with stale ports and the only way to find the issue out is to gdb into
    the process which is always not available. This patch attempts to fill
    in this gap.
    
    >Reviewed-on: https://review.gluster.org/16764
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Prashanth Pai <ppai>
    >(cherry picked from commit dbdfe6c353060b7af7b4250c8d6c30ed0c35783c)
    
    Change-Id: I26b4fe753d752366ddf865ca3eeae3b4d577d555
    BUG: 1427399
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: https://review.gluster.org/16779
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Prashanth Pai <ppai>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-04-05 00:01:42 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.10.1, please open a new bug report.

glusterfs-3.10.1 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://lists.gluster.org/pipermail/gluster-users/2017-April/030494.html
[2] https://www.gluster.org/pipermail/gluster-users/