Bug 1095594

Summary: Stick to IANA standard while allocating brick ports
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: protocolAssignee: Joe Julian <joe>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: mainlineCC: amarts, bugs, gluster-bugs, joe, ujjwala, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 824233 Environment:
Last Closed: 2014-11-11 08:32:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: DP CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Julian 2014-05-08 06:04:59 UTC
This change needs documented in doc/admin-guide/en-US/markdown/admin_monitoring_workload.md, doc/admin-guide/en-US/markdown/admin_settingup_clients.md, and doc/glusterfsd.8


+++ This bug was initially created as a clone of Bug #824233 +++

Description of problem:
Ref: RFC 6335
Use ports above 49152 for bricks as they are in the private range.

--- Additional comment from Amar Tumballi on 2012-05-24 23:49:20 EDT ---

fixed by patch http://review.gluster.com/3339

--- Additional comment from Amar Tumballi on 2012-06-01 02:54:01 EDT ---

the bug fix is only in upstream, not in release-3.3. Hence moving it out of the ON_QA, and setting MODIFIED (as a standard practice @ Red Hat)

--- Additional comment from Joe Julian on 2014-05-08 02:01:39 EDT ---

This change lacks documentation.

Comment 1 Anand Avati 2014-05-22 17:29:00 UTC
REVIEW: http://review.gluster.org/7852 (doc: Fix peer probe deficiencies) posted (#1) for review on master by Joe Julian (me)

Comment 2 Anand Avati 2014-05-23 19:57:06 UTC
REVIEW: http://review.gluster.org/7852 (doc: Fix peer probe deficiencies) posted (#2) for review on master by Joe Julian (me)

Comment 3 Anand Avati 2014-06-14 00:51:20 UTC
REVIEW: http://review.gluster.org/7852 (doc: Fix peer probe deficiencies) posted (#3) for review on master by Joe Julian (me)

Comment 4 Anand Avati 2014-06-14 00:57:27 UTC
REVIEW: http://review.gluster.org/7852 (doc: Fix peer probe deficiencies) posted (#4) for review on master by Joe Julian (me)

Comment 5 Anand Avati 2014-06-14 13:50:04 UTC
COMMIT: http://review.gluster.org/7852 committed in master by Vijay Bellur (vbellur) 
------
commit ced0dcd817d02ce7ea2b69bff94dad26a96efe71
Author: Joe Julian <me>
Date:   Thu May 22 10:24:22 2014 -0700

    doc: Fix peer probe deficiencies
    
    Added the command to probe the first server to assign it a hostname
    
    Change-Id: I9c25f1ce3175e1ffe024f6b6ae14a4526228489a
    BUG: 1095594
    Reviewed-on: http://review.gluster.org/7852
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 6 Niels de Vos 2014-09-22 12:39:56 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 7 Niels de Vos 2014-11-11 08:32:05 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users