Red Hat Bugzilla – Bug 1256352
gluster-nfs : contents of export file is not updated correctly in its context
Last modified: 2016-06-16 09:33:12 EDT
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):
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.
Servers allow write operation
Server should not allow write operation.
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
REVIEW: http://review.gluster.org/12006 (tests : workaround for the spourious failure in mount-nfs-auth.t) posted (#2) for review on master by jiffin tony Thottan (email@example.com)
REVIEW: http://review.gluster.org/12006 (tests : workaround for the spurious failure in mount-nfs-auth.t) posted (#3) for review on master by Raghavendra Talur (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12006 committed in master by Niels de Vos (email@example.com)
Author: Jiffin Tony Thottan <firstname.lastname@example.org>
Date: Mon Aug 24 18:01:19 2015 +0530
tests : workaround for the spurious failure in mount-nfs-auth.t
Signed-off-by: Jiffin Tony Thottan <email@example.com>
Reviewed-by: Niels de Vos <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.