Bug 1703753

Summary: portmap entries missing in glusterd statedumps
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: glusterdAssignee: Sanju <srakonde>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amukherj, pasik, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone: ---Keywords: Regression
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:20:55 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: 1703759    
Bug Blocks: 1696807    
Attachments:
Description Flags
new statedump none

Description Nag Pavan Chilakam 2019-04-28 06:37:26 UTC
Created attachment 1559580 [details]
new statedump

Description of problem:
=========================
portmap entries are missing in glusterd statedumps.
Statedumps capture portmap details which is useful especially in a brick multiplexed setup including OCS, for debugging.
This was previously existing, and hence a regression

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

How reproducible:
==================
always

Steps to Reproduce:
1.created a brickmux setup, and created an ec volume 20x(4+2)
2.took a statedump (either use kill -USR1 $(pgrep glusterd) or statedump command )
3. scan the glusterd statedump file which is generally available in /var/run/gluster/


Actual results:
==================
I don't see any portmap details which used to exist previously

Comment 9 errata-xmlrpc 2019-10-30 12:20:55 UTC
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/RHEA-2019:3249