Bug 1614739

Summary:	ssh connection timeout issue for uploading logs
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, 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:	2018-08-10 10:55:56 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 Pranith Kumar K 2018-08-10 10:19:21 UTC

Description of problem:
I am looking at https://build.gluster.org/job/regression-on-demand-multiplex/201/consoleFull to get the location of logs and I see the following logs

"18:47:49 + scp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /home/jenkins/root/workspace/regression-on-demand-multiplex/ glusterfs-logs.tgz _logs_collector.rht.gluster.org:/var/www/glusterfs-logs/regression-on-demand-multiplex-201.tgz 18:49:56
ssh: connect to host http.int.rht.gluster.org port 22: Connection timed out 18:49:56 lost connection"

I am not sure if it is a bug. Raising it just in case.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nigel Babu 2018-08-10 10:55:56 UTC

It's a bug yes, but you still have logs. This is a failing step in our efforts to put logs on  a central machine.

Example job: https://build.gluster.org/job/centos7-regression/2201/
If you search for "Build artifacts" on that page, you should see the logs.