+++ This bug was initially created as a clone of Bug #1018894 +++ Description of problem: The ability to use "*" as a wildcard in the "nfs.rpc-auth-allow", and "nfs.rpc-auth-reject" list. Version-Release number of selected component (if applicable): glusterfs-server-3.4.0.33rhs-1 How reproducible: Consistently Steps to Reproduce: 1. Create a Gluster volume 2. Run the "gluster volume set <VOL_NAME> nfs.rpc-auth-allow *.example.com Actual results: [root@rhsn1 ~]# gluster volume set rep_test_vol00 nfs.rpc-auth-allow *.example.com volume set: failed: option rpc-auth.addr.rep_test_vol00.allow *.example.com: '*.example.com' is not a valid internet-address-list Expected results: volume set: success Additional Information: N/A --- Additional comment from Sayan Saha on 2014-01-23 16:22:33 EST --- Target this for Denali
REVIEW: http://review.gluster.org/7431 (common-utils: valid_host_name() now allows wildcards(*/?/[]) in hostname.) posted (#1) for review on master by Poornima G (pgurusid)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#1) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#2) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#3) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#4) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#5) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#6) for review on master by Santosh Pradhan (spradhan)
REVIEW: http://review.gluster.org/7485 (gNFS: Support wildcard in RPC auth allow/reject) posted (#7) for review on master by Santosh Pradhan (spradhan)
COMMIT: http://review.gluster.org/7485 committed in master by Vijay Bellur (vbellur) ------ commit 00e247ee44067f2b3e7ca5f7e6dc2f7934c97181 Author: Santosh Kumar Pradhan <spradhan> Date: Wed Apr 9 10:19:43 2014 +0530 gNFS: Support wildcard in RPC auth allow/reject RFE: Support wildcard in "nfs.rpc-auth-allow" and "nfs.rpc-auth-reject". e.g. *.redhat.com 192.168.1[1-5].* 192.168.1[1-5].*, *.redhat.com, 192.168.21.9 Along with wildcard, support for subnetwork or IP range e.g. 192.168.10.23/24 The option will be validated for following categories: 1) Anonymous i.e. "*" 2) Wildcard pattern i.e. string containing any ('*', '?', '[') 3) IPv4 address 4) IPv6 address 5) FQDN 6) subnetwork or IPv4 range Currently this does not support IPv6 subnetwork. Change-Id: Iac8caf5e490c8174d61111dad47fd547d4f67bf4 BUG: 1086097 Signed-off-by: Santosh Kumar Pradhan <spradhan> Reviewed-on: http://review.gluster.org/7485 Reviewed-by: Poornima G <pgurusid> Reviewed-by: Harshavardhana <harsha> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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/
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