DescriptionAndrew 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.
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.