Bug 1685813

Summary:	Not able to run centos-regression getting exception error
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs, gluster-infra, mscherer, pasik, sankarshan
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:	2019-05-27 02:11:15 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 Mohit Agrawal 2019-03-06 07:50:10 UTC

Description of problem:
Not able to run centos-regression build is getting an Exception error

Version-Release number of selected component (if applicable):


How reproducible:

https://build.gluster.org/job/centos7-regression/5017/consoleFull
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 M. Scherer 2019-03-06 09:45:53 UTC

Yeah, there is a patch that seems to break builders one by one. 

Dkhandel told me this morning that we lost lots of aws builder (8 out of 10), and upon investigation, they all ran regression tests for that change before becoming offline:

https://review.gluster.org/#/c/glusterfs/+/22290/

As said on gerrit, I strongly suspect that the logic change do result in the test spawning a infinite loop, since the builder we recovered didn't show any trace of error in the log, which is the kind of symptom you get with a infinite loop (while still answering to ping, since icmp is handled in the kernel). 

So I would suggest to investigate ./tests/00-geo-rep/00-georep-verify-setup.t , as I see that as being the last test run before losing contact with builders. In fact, since the patch worked for the 2nd iteration, I guess the issue is the 3rd iteration of the patch.

In any case, I think that's not a infra issue.

Comment 2 M. Scherer 2019-03-06 10:53:31 UTC

I did reboot the broken builders and they are back. And I also looked at the patch, but didn't found something, so I suspect there is some logic that escape me.

Comment 3 Mohit Agrawal 2019-03-06 10:58:53 UTC

Thanks, Michael there is some issue in my patch.
I will upload a new patch.
You can close the bugzilla.

Thanks,
Mohit Agrawal