Bug 1321916

Summary:	auth.allow and auth.reject option should accept ip address with negation !
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.x	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-11 02:05:52 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:
Bug Depends On:
Bug Blocks:	1321921

Description Gaurav Kumar Garg 2016-03-29 11:30:35 UTC

Description of problem:

Currently when user set auth.allow and auth.reject option with negation followed by ip-address (for eg:  !192.168.x.x) then Gluster is not accepting that ip address.

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

How reproducible:
every time.

Steps to Reproduce:
set auth.allow or auth.reject option with negation ip-address



Expected results:

It should allow setting of auth.allow/auth.reject option with negation.

Comment 1 Vijay Bellur 2016-03-30 12:59:17 UTC

REVIEW: http://review.gluster.org/13855 (libglusterfs: supporting ip-address or hostname with negation) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Vijay Bellur 2016-04-04 10:13:44 UTC

REVIEW: http://review.gluster.org/13855 (libglusterfs: supporting ip-address or hostname with negation) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)

Comment 5 Amar Tumballi 2019-05-11 02:05:52 UTC

We have added tests to validate the options, and ! works.