Bug 765247 (GLUSTER-3515) - Volume specific nfs.insecure-ports option does not allow mounts from insecure ports
Summary: Volume specific nfs.insecure-ports option does not allow mounts from insecure...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3515
Product: GlusterFS
Classification: Community
Component: nfs
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-06 10:21 UTC by Shehjar Tikoo
Modified: 2011-09-22 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: nfs
Documentation: DNR
CRM:
Verified Versions: 3.2.4qa2
Embargoed:

Attachments (Terms of Use)

Description Shehjar Tikoo 2011-09-06 10:21:26 UTC 
This is a bug in the handling on nfs.insecure-ports option in nfs-rpc. When set using the volume-specific fashion, it still does not allow a mount from an unprivileged port to connect using the -o noresvport option with mount command.
Comment 1 Anand Avati 2011-09-12 10:26:02 UTC 
CHANGE: http://review.gluster.com/356 (Change-Id: Ia53f64e923babdd3af2d82b13350c97fa25fac2d) merged in release-3.1 by Vijay Bellur (vijay)
Comment 2 Anand Avati 2011-09-12 10:26:55 UTC 
CHANGE: http://review.gluster.com/355 (Change-Id: Ia53f64e923babdd3af2d82b13350c97fa25fac2d) merged in release-3.2 by Vijay Bellur (vijay)
Comment 3 Anand Avati 2011-09-19 02:17:28 UTC 
CHANGE: http://review.gluster.com/418 (Change-Id: Ica59a3154c4e7d980d3477dd3879c7cebe92ad87) merged in master by Vijay Bellur (vijay)
Comment 4 Vijaykumar 2011-09-21 06:54:22 UTC 
I verified it on release-3.2.4qa2. Its working fine now. 
I want to know, why it is still in assigned state, can it be moved resolved fixed and verified fixed?
Note You need to log in before you can comment on or make changes to this bug.