Bug 1601594 - Glusterfs brick ports outside documented range
Summary: Glusterfs brick ports outside documented range
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Installation_Guide
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.4.z Async Update
Assignee: Laura Bailey
QA Contact: Kshithij Iyer
URL:
Whiteboard:
Depends On:
Blocks: 1650394
TreeView+ depends on / blocked
 
Reported: 2018-07-16 19:36 UTC by Andrew Robinson
Modified: 2019-06-19 06:42 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-28 10:21:49 UTC
Embargoed:

Attachments (Terms of Use)
Screenshot showing brick ports outside of the documented range. (189.15 KB, image/jpeg)
2018-07-16 19:36 UTC, Andrew Robinson 		no flags Details
View All

Description Andrew Robinson 2018-07-16 19:36:41 UTC 
Created attachment 1459252 [details]
Screenshot showing brick ports outside of the documented range.

Description of problem:

After restarting volume, the brick ports for the volume were 49252-49256. According to the installation guide, the ports should be in the range 49152 - 49251


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

RHGS 3.2


How reproducible:

Happened when volume stopped and started


Steps to Reproduce:
1. Run 'gluster volume stop'
2. Run 'gluster volume start'
3. Run 'gluster volume status'

Actual results:

Mount attempt from client failed because firewall blocking ports


Expected results:

Brick ports would be in the documented range so the mount command from the client would succeed. 

Additional info:

When the volume was restarted a second time, the brick ports returned to the documented range. The "illegal" range is documented in the attached screenshot.
Note You need to log in before you can comment on or make changes to this bug.