Red Hat Bugzilla – Bug 765247
Volume specific nfs.insecure-ports option does not allow mounts from insecure ports
Last modified: 2011-09-22 03:31:54 EDT
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.
CHANGE: http://review.gluster.com/356 (Change-Id: Ia53f64e923babdd3af2d82b13350c97fa25fac2d) merged in release-3.1 by Vijay Bellur (email@example.com)
CHANGE: http://review.gluster.com/355 (Change-Id: Ia53f64e923babdd3af2d82b13350c97fa25fac2d) merged in release-3.2 by Vijay Bellur (firstname.lastname@example.org)
CHANGE: http://review.gluster.com/418 (Change-Id: Ica59a3154c4e7d980d3477dd3879c7cebe92ad87) merged in master by Vijay Bellur (email@example.com)
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?