[Gluster-infra] [Bug 1435254] New: arbiter-mount.t is nuking everyone's regression tests

bugzilla at redhat.com bugzilla at redhat.com
Thu Mar 23 13:23:47 UTC 2017


            Bug ID: 1435254
           Summary: arbiter-mount.t is nuking everyone's regression tests
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Assignee: bugs at gluster.org
          Reporter: jeff at pl.atyp.us
                CC: bugs at gluster.org, gluster-infra at gluster.org

All of these seem to have failed spuriously because of rpc.statd not running. 
Also, all of the ones I've looked at seemed to be on slave25.

https://build.gluster.org/job/centos6-regression/3727/console (tier)
https://build.gluster.org/job/centos6-regression/3728/console (glusterd)
https://build.gluster.org/job/centos6-regression/3732/console (glusterd)
https://build.gluster.org/job/centos6-regression/3732/console (readdir-ahead)
https://build.gluster.org/job/centos6-regression/3734/console (readdir-ahead)
https://build.gluster.org/job/centos6-regression/3735/console (afr)
https://build.gluster.org/job/centos6-regression/3736/console (glusterd)

So, is it an infrastructure issue, or related to the recent Ganesha mega-patch?
 That's not clear.  Assigning to infra initially because I can test that
hypothesis by disabling slave25 so the next test will run somewhere else.  If
it fails there too, it's more likely to be an nfs issue.

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Bq4avCbPpD&a=cc_unsubscribe

More information about the Gluster-infra mailing list