[Bugs] [Bug 1256352] New: gluster-nfs : contents of export file is not updated correctly in its context

bugzilla at redhat.com bugzilla at redhat.com
Mon Aug 24 12:08:58 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1256352

            Bug ID: 1256352
           Summary: gluster-nfs : contents of export file is not updated
                    correctly in its context
           Product: GlusterFS
           Version: mainline
         Component: nfs
          Keywords: Triaged
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: jthottan at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

The following tests(50,51) in mount-nfs-auth.t were failing spuriously for
NETBSD machines. In those tests, nfs client is only allowed for reads. Here
even though export file is updated correctly but it is not reflected in
nfs-server context. So write will be allowed for those clients.

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

How reproducible:
10% when mount-nfs-auth.t executed in NETBSD machine.(Spurious failure)

Steps to Reproduce:
Run mount-nfs-auth.t in infinite loop . The test will fail at 50,51 cases(which
checks for read-only client) at some point.

Actual results:
Servers allow write operation 

Expected results:
Server should not allow write operation.

Additional info:

It seems to be when contents of export file are updated , then
_mnt3_auth_param_refresh_thread() should call _mnt3_has_file_changed(). But it
is not happening for those above mentioned tests which can be understand from
nfs-server log.

The following logs were missing after updating the export file :

[MSGID: 112147] [mount3.c:3720:_mnt3_auth_param_refresh_thread] 0-nfs-mount:
File /autobuild/install/var/db/glusterd/nfs/exports changed, updating exports,

[MSGID: 112151] [mount3.c:3752:_mnt3_auth_param_refresh_thread] 0-nfs-mount:
Purging auth cache

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list