+++ This bug was initially created as a clone of Bug #1319271 +++ Description of problem: ----------------------- auth.allow and auth.reject not taking in values of hostnames when mentioned with FQDNs, but works with IPv4 Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Set auth.allow or auth.reject with FQDN Actual results: --------------- auth.allow or auth.reject doesn't work with the hostnames when provided with FQDN Expected results: ----------------- auth.allow or auth.reject should accept/respect the hostnames when provided with FQDN
REVIEW: http://review.gluster.org/13835 (protocol: resolve hostname or ip address properly while authentication) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
REVIEW: http://review.gluster.org/13835 (protocol: resolve hostname or ip address properly while authentication) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/13835 (protocol: resolve hostname or ip address properly while authentication) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/13835 (protocol: resolve hostname or ip address properly while authentication) posted (#4) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/15086 (cli : auth.allow and auth.reject does not accept FQDN/host name) posted (#1) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli : auth.allow and auth.reject does not accept FQDN/host name) posted (#2) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli : auth.allow and auth.reject does not accept FQDN/host name) posted (#3) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli/auth : auth.allow and auth.reject does not accept FQDN/host name) posted (#4) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli/auth : auth.allow and auth.reject does not accept FQDN/host name) posted (#5) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli/auth : auth.allow and auth.reject does not accept FQDN/host name) posted (#6) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: http://review.gluster.org/15086 (cli/auth : auth.allow and auth.reject does not accept FQDN/host name) posted (#7) for review on master by MOHIT AGRAWAL (moagrawa)
REVIEW: https://review.gluster.org/15086 (cli/auth : auth.allow and auth.reject does not accept FQDN/host name) posted (#8) for review on master by MOHIT AGRAWAL (moagrawa)
COMMIT: https://review.gluster.org/15086 committed in master by Raghavendra G (rgowdapp) ------ commit c7ba4b2b1a1cca6f217083ff9c1f01f23c9ca171 Author: Mohit Agrawal <moagrawa> Date: Thu Mar 30 14:45:59 2017 +0530 cli/auth : auth.allow and auth.reject does not accept FQDN/host name Problem : At the time of set FQDN name to "auth.allow/auth.reject" through gluster cli,it does not accept FQDN/host name. Solution: Condition needs to be update in verify_host_name and gf_auth to accept FQDN/host name. Fix : Change the condition to accept FQDN/host Name. To verify the patch followed below procedure 1) Try to set FQDN name for auth.allow or auth.reject parameter gluster v set myvol auth.reject <fqdn name> It gives error "fqdn-name" is not a valid internet-address-list 2) After apply the patch it does not give any error. 3) To verify auth.allow/reject try to mount volume on some client. Change-Id: Ieb76cbb93d43323fd29c7ca04efe3790edb4281b BUG: 1321578 Signed-off-by: Mohit Agrawal <moagrawa> Reviewed-on: https://review.gluster.org/15086 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra G <rgowdapp>
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.11.0, please open a new bug report. glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/