Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings
I assume we build with --enable-gnfs turned on. Unlikely that its not, but just pointing it out as initially I ran into some failures due to gNFS server not coming due to lake of relevant libraries. On Thu, Mar 15, 2018 at 3:46 PM, Raghavendra Gowdappa wrote: > Providing more links to failure: > https://build.gluster.org/job/experimental-periodic/227/console > https://build.gluster.org/job/regression-test-burn-in/3836/console > > > On Thu, Mar 15, 2018 at 3:39 PM, Raghavendra Gowdappa > wrote: > >> I can reproduce the failure even without my patch on master. Looks like >> this test resulted in failures earlier too. >> >> [1] http://lists.gluster.org/pipermail/gluster-devel/2015-May/044932.html >> [2] See mail to gluster-maintainers with subj: "Build failed in Jenkins: >> regression-test-burn-in #3836" >> >> Usual failures are (need not be all of them, but at least few of them): >> ./tests/basic/mount-nfs-auth.t (Wstat: 0 Tests: 92 Failed: 4) >> Failed tests: 22-24, 28 >> >> If gNFS team can take a look into this it will be helpful. >> >> regards, >> Raghavendra >> >> On Wed, Mar 14, 2018 at 3:04 PM, Nigel Babu wrote: >> >>> 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 < >>> rgowd...@redhat.com> wrote: >>> All, 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= To debug I ran the volume get cmds: [root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab Option Value -- - 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 Option Value -- - nfs.mount-rmtab testdir Does this mean the option value is not set properly in the script? Need your help in debugging this. @Nigel I noticed that test is timing out. *20:28:39* ./tests/basic/mount-nfs-auth.t timed out after 200 seconds Can this be infra issue where nfs was taking too much time to mount? [1] https://build.gluster.org/job/centos7-regression/316/console regards, Raghavendra >>> >>> >>> >>> -- >>> nigelb >>> >> >> > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > -- Raghavendra G ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings
Providing more links to failure: https://build.gluster.org/job/experimental-periodic/227/console https://build.gluster.org/job/regression-test-burn-in/3836/console On Thu, Mar 15, 2018 at 3:39 PM, Raghavendra Gowdappa wrote: > I can reproduce the failure even without my patch on master. Looks like > this test resulted in failures earlier too. > > [1] http://lists.gluster.org/pipermail/gluster-devel/2015-May/044932.html > [2] See mail to gluster-maintainers with subj: "Build failed in Jenkins: > regression-test-burn-in #3836" > > Usual failures are (need not be all of them, but at least few of them): > ./tests/basic/mount-nfs-auth.t (Wstat: 0 Tests: 92 Failed: 4) > Failed tests: 22-24, 28 > > If gNFS team can take a look into this it will be helpful. > > regards, > Raghavendra > > On Wed, Mar 14, 2018 at 3:04 PM, Nigel Babu wrote: > >> 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 < >> rgowd...@redhat.com> wrote: >> >>> All, >>> >>> 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= >>> >>> To debug I ran the volume get cmds: >>> >>> [root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab >>> Option Value >>> >>> -- - >>> >>> 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 >>> Option Value >>> >>> -- - >>> >>> nfs.mount-rmtab testdir >>> >>> >>> Does this mean the option value is not set properly in the script? Need >>> your help in debugging this. >>> >>> @Nigel >>> I noticed that test is timing out. >>> >>> *20:28:39* ./tests/basic/mount-nfs-auth.t timed out after 200 seconds >>> >>> Can this be infra issue where nfs was taking too much time to mount? >>> >>> [1] https://build.gluster.org/job/centos7-regression/316/console >>> >>> regards, >>> Raghavendra >>> >> >> >> >> -- >> nigelb >> > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings
I can reproduce the failure even without my patch on master. Looks like this test resulted in failures earlier too. [1] http://lists.gluster.org/pipermail/gluster-devel/2015-May/044932.html [2] See mail to gluster-maintainers with subj: "Build failed in Jenkins: regression-test-burn-in #3836" Usual failures are (need not be all of them, but at least few of them): ./tests/basic/mount-nfs-auth.t (Wstat: 0 Tests: 92 Failed: 4) Failed tests: 22-24, 28 If gNFS team can take a look into this it will be helpful. regards, Raghavendra On Wed, Mar 14, 2018 at 3:04 PM, Nigel Babu wrote: > 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 < > rgowd...@redhat.com> wrote: > >> All, >> >> 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= >> >> To debug I ran the volume get cmds: >> >> [root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab >> Option Value >> >> -- - >> >> 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 >> Option Value >> >> -- - >> >> nfs.mount-rmtab testdir >> >> >> Does this mean the option value is not set properly in the script? Need >> your help in debugging this. >> >> @Nigel >> I noticed that test is timing out. >> >> *20:28:39* ./tests/basic/mount-nfs-auth.t timed out after 200 seconds >> >> Can this be infra issue where nfs was taking too much time to mount? >> >> [1] https://build.gluster.org/job/centos7-regression/316/console >> >> regards, >> Raghavendra >> > > > > -- > nigelb > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings
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 wrote: > All, > > 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= > > To debug I ran the volume get cmds: > > [root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab > Option Value > > -- - > > 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 > Option Value > > -- - > > nfs.mount-rmtab testdir > > > Does this mean the option value is not set properly in the script? Need > your help in debugging this. > > @Nigel > I noticed that test is timing out. > > *20:28:39* ./tests/basic/mount-nfs-auth.t timed out after 200 seconds > > Can this be infra issue where nfs was taking too much time to mount? > > [1] https://build.gluster.org/job/centos7-regression/316/console > > regards, > Raghavendra > -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings
All, 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= To debug I ran the volume get cmds: [root@booradley glusterfs]# gluster volume get patchy nfs.mount-rmtab Option Value -- - 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 Option Value -- - nfs.mount-rmtab testdir Does this mean the option value is not set properly in the script? Need your help in debugging this. @Nigel I noticed that test is timing out. *20:28:39* ./tests/basic/mount-nfs-auth.t timed out after 200 seconds Can this be infra issue where nfs was taking too much time to mount? [1] https://build.gluster.org/job/centos7-regression/316/console regards, Raghavendra ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel