+++ 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)
upstream patch : https://review.gluster.org/16764
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101321
verified in version 3.8.4.22 In glusterd statedump, brick and port related details also dumped as below glusterd.pmap_port=49153 glusterd.pmap[49153].type=4 glusterd.pmap[49153].brickname=/bricks/brick1/t21 glusterd.pmap_port=49154 glusterd.pmap[49154].type=4 glusterd.pmap[49154].brickname=/bricks/brick1/t24 glusterd.pmap_port=49155 Hence marking the bug as verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774