Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1435254

Summary:	arbiter-mount.t is nuking everyone's regression tests
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jeff>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, misc, nigelb
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-23 15:04:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Darcy 2017-03-23 13:23:47 UTC

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.

Comment 1 Jeff Darcy 2017-03-23 14:16:57 UTC

Test ran on slave1 this time and seems to be fine, so I'll leave slave25 down and leave this as an infra issue.

Comment 2 Nigel Babu 2017-03-23 15:04:19 UTC

Sorry! I've just started it.

Comment 3 Nigel Babu 2017-03-23 15:04:52 UTC

rpcbind started and machine back in the pool.

Comment 4 Michael S. 2017-03-23 16:20:45 UTC

yeah, seems that slave25 had a corrupted rpm db, and this did prevent ansible from running fully. I did fixed that yesterday, I am not sure when this did start.