Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1337127

Summary:	rpc: change client insecure port ceiling from 65535 to 49151
Product:	[Community] GlusterFS	Reporter:	Prasanna Kumar Kalever <prasanna.kalever>
Component:	rpc	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1335776	Environment:
Last Closed:	2016-06-16 14:07:31 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:

Description Prasanna Kumar Kalever 2016-05-18 10:56:15 UTC

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

Description of problem:
current port allocation to various processes (clumsy):
    
 1023 - 1       -> client ports range if bind secure is turned on
49151 - 1024    -> fall back to this, if in above case ports exhaust
65535 - 1024    -> client port range if bind insecure is on
49152 - 65535   -> brick port range
    
now, we should have segregated port ranges 0 - 65535 to below 3 ranges
    
 1023 - 1       -> client ports range if bind secure is turned on
49151 - 1024    -> client port range if bind insecure is on
                   (fall back to this, if in above case ports exhaust)
49152 - 65535   -> brick port range
    
for a cleaner way of segregation this is necessary, and since  bind insecure
is on by default, there could be a chance of port clashes between brick and clients

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

--- Additional comment from Vijay Bellur on 2016-05-13 04:20:20 EDT ---

REVIEW: http://review.gluster.org/14326 (rpc: change client insecure port ceiling from 65535 to 49151) posted (#1) for review on master by Prasanna Kumar Kalever (pkalever)

--- Additional comment from Vijay Bellur on 2016-05-18 06:26:04 EDT ---

COMMIT: http://review.gluster.org/14326 committed in master by Raghavendra G (rgowdapp) 
------

Comment 1 Vijay Bellur 2016-05-18 10:58:11 UTC

REVIEW: http://review.gluster.org/14413 (rpc: change client insecure port ceiling from 65535 to 49151) posted (#1) for review on release-3.8 by Prasanna Kumar Kalever (pkalever)

Comment 2 Vijay Bellur 2016-05-19 08:56:56 UTC

COMMIT: http://review.gluster.org/14413 committed in release-3.8 by Raghavendra G (rgowdapp) 
------
commit e208128e38cc62fc9812bc1f9ffb09be8329f698
Author: Prasanna Kumar Kalever <prasanna.kalever>
Date:   Fri May 13 13:17:16 2016 +0530

    rpc: change client insecure port ceiling from 65535 to 49151
    
    current port allocation to various processes (clumsy):
    
     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> fall back to this, if in above case ports exhaust
    65535 - 1024    -> client port range if bind insecure is on
    49152 - 65535   -> brick port range
    
    now, we have segregated port ranges 0 - 65535 to below 3 ranges
    
     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> client port range if bind insecure is on
                       (fall back to this, if in above case ports exhaust)
    49152 - 65535   -> brick port range
    
    so now we have a clean segregation of port mapping
    
    Backport of:
    > Change-Id: Ie3b4e7703e0bbeabbe0adbdd6c60d9ef78ef7c65
    > BUG: 1335776
    > Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever>
    > Reviewed-on: http://review.gluster.org/14326
    > Tested-by: Prasanna Kumar Kalever <pkalever>
    > Reviewed-by: Raghavendra Talur <rtalur>
    > Tested-by: Gluster Build System <jenkins.com>
    > CentOS-regression: Gluster Build System <jenkins.com>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Smoke: Gluster Build System <jenkins.com>
    > Reviewed-by: Kaleb KEITHLEY <kkeithle>
    > Reviewed-by: Raghavendra G <rgowdapp>
    
    Change-Id: Ie3b4e7703e0bbeabbe0adbdd6c60d9ef78ef7c65
    BUG: 1337127
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever>
    Reviewed-on: http://review.gluster.org/14413
    Tested-by: Prasanna Kumar Kalever <pkalever>
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 3 Niels de Vos 2016-06-16 14:07:31 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.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user