Bug 1493387

Summary:	java.io.EOFException prevents launching of regression tests
Product:	[Community] GlusterFS	Reporter:	Anoop C S <anoopcs>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-20 06:34:02 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 Anoop C S 2017-09-20 05:50:16 UTC

Description of problem:
Regression tests failed to start for the following review request:
https://review.gluster.org/#/c/18325/

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

How reproducible:
2/2

Steps to Reproduce:
1. Comment "recheck centos" on https://review.gluster.org/#/c/18325/

Actual results:
Immediate reply from build system indicating failure to start regression run.

Expected results:
Regression tests should be launched successfully.

Additional info:
Specific build links:
Ist try: https://build.gluster.org/job/centos6-regression/6482/console
2nd try: https://build.gluster.org/job/centos6-regression/6485/console

Comment 1 Nigel Babu 2017-09-20 06:34:02 UTC

After this test run, the centos node was left with a lot of long-running gluster processes: https://build.gluster.org/job/regression-test-with-multiplex/354/console

I've pkilled all the processes, rebooted the node and put it back in the pool. It should be back to normal now.

Comment 2 Nigel Babu 2017-09-20 06:46:06 UTC

For future reference, after fixing up the server, it needs to be disconnected from Jenkins and connected back. That's when the channel information refreshes.