Bug 1703753 - portmap entries missing in glusterd statedumps
Summary: portmap entries missing in glusterd statedumps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.5.0
Assignee: Sanju
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1703759
Blocks: 1696807
TreeView+ depends on / blocked
 
Reported: 2019-04-28 06:37 UTC by Nag Pavan Chilakam
Modified: 2019-10-30 13:01 UTC (History)
6 users (show)

Fixed In Version: glusterfs-6.0-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:20:55 UTC
Embargoed:


Attachments (Terms of Use)
new statedump (54.90 KB, text/plain)
2019-04-28 06:37 UTC, Nag Pavan Chilakam
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:21:18 UTC

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


Note You need to log in before you can comment on or make changes to this bug.