When the test works it takes less than 60 seconds. If it needs more than 200 seconds, that means there's an actual issue.
On Wed, Mar 14, 2018 at 10:16 AM, Raghavendra Gowdappa <rgowdapp@xxxxxxxxxx> wrote:
Does this mean the option value is not set properly in the script? Need your help in debugging this.All,To debug I ran the volume get cmds:
I was trying to debug a regression failure [1]. When I ran test locally on my laptop, I see some warnings as below:
++ gluster --mode=script --wignore volume get patchy nfs.mount-rmtab
++ xargs dirname
++ awk '/^nfs.mount-rmtab/{print $2}'
dirname: missing operand
Try 'dirname --help' for more information.
+ NFSDIR=
[root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab
OptionValue
-----------
volume get option failed. Check the cli/glusterd log file for more details
[root@booradley glusterfs]# gluster volume set patchy nfs.mount-rmtab testdir
volume set: success
[root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab
OptionValue
-----------
nfs.mount-rmtabtestdir @NigelI noticed that test is timing out.Can this be infra issue where nfs was taking too much time to mount? ./tests/basic/mount-nfs-auth.t timed out after 200 seconds
--
nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel