Bug 974417 - BVT: Validation of volume set option "auth.reject" in vol file Failed
Summary: BVT: Validation of volume set option "auth.reject" in vol file Failed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.1
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Kaushal
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-14 07:31 UTC by Lalatendu Mohanty
Modified: 2013-06-24 12:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-24 12:35:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Lalatendu Mohanty 2013-06-14 07:31:39 UTC
Description of problem:

Validation of set option "auth.reject" in brick vol file Failed  

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


How reproducible:


Steps to Reproduce:
    Running 'gluster volume set volume-set auth.reject 192.168.1.78'

:: [ 21:17:36 ] ::  Executing validation in volume info

:: [   PASS   ] :: Validation of set option auth.reject in volume info is      Successful

:: [ 21:17:37 ] ::  Executing validation in volume file
:: [   FAIL   ] :: Validation of set option auth.reject in vol file is Failed  

Actual results:


Expected results:


Additional info:

Comment 2 Kaushal 2013-06-20 05:52:15 UTC
What pattern are you searching for in the vol files? The auth.addr & auth.reject options are present in the brick volfiles only and have the pattern,

  option auth.addr.<brickpath>.{allow,reject} <value>

So, if on a volume 'test' is created with one brick 'host:/export/brick1', you set the option 'auth.allow' to 'example.com' , you will need to search for
  option auth.addr./export/brick1.allow example.org
in the volfile /var/lib/gluster/vols/test/test.host.export-brick.vol

Comment 3 Lalatendu Mohanty 2013-06-24 12:35:13 UTC
It is an automation code issue. Closing the bug


Note You need to log in before you can comment on or make changes to this bug.