Bug 798917 - volume set auth.allow * not working
Summary: volume set auth.allow * not working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Rajesh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 09:22 UTC by Shwetha Panduranga
Modified: 2013-07-04 22:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-26 07:52:49 UTC
Regression: ---
Mount Type: ---
Documentation: DP
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.