Bug 798917

Summary:	volume set auth.allow * not working
Product:	[Community] GlusterFS	Reporter:	Shwetha Panduranga <shwetha.h.panduranga>
Component:	cli	Assignee:	Rajesh <rajesh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	amarts, gluster-bugs, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-26 07:52:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	DP	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Shwetha Panduranga 2012-03-01 09:22:08 UTC

Description of problem:
gluster volume set <volume_name> auth.allow * Not Working. 
This is required if we have set auth.allow to a ip_address/Hostname and we need to re-change the auth.allow to all ip_addresses/Hostnames. 

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

How reproducible:
often

  
Actual results:
Usage: volume set <VOLNAME> <KEY> <VALUE>

Expected results:
Should all the * wild character. 

Additional info:

Comment 1 Amar Tumballi 2012-03-01 10:19:19 UTC

can you try 'gluster volume reset <VOLNAME> <KEY>' and see if it gets reset?

Comment 2 Shwetha Panduranga 2012-03-01 12:26:45 UTC

yes, it works.

Comment 3 Amar Tumballi 2012-03-12 07:33:20 UTC

reducing the priority as there exists a work around.

Comment 4 Rajesh 2012-04-26 07:52:49 UTC

when we do gluster volume set <volname> auth.allow *,
bash, or any other shell tries to expand the "*", which is a wildcard character.
escaping it with "\" works fine.

Comment 5 Amar Tumballi 2012-04-26 08:38:49 UTC

Rajesh, good find. Make sure we document this properly.