Bug 1328550

Summary:	TLS error trying to clone gits using https from gitlab
Product:	[Retired] Restraint	Reporter:	Vimal Patel <vipatel>
Component:	general	Assignee:	Artem Savkov <asavkov>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.1.24	CC:	asavkov, bpeck, dcallagh, jhutar, mjia, qsong, rjoost
Target Milestone:	0.1.28
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-07 09:36:08 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:

Description Vimal Patel 2016-04-19 15:57:02 UTC

Description of problem:
attempting to run a task using https from gitlab fails
(https://gitlab.cee.redhat.com/satellite5qe/RHN-Satellite.git)

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

How reproducible:
100%

Steps to Reproduce:
1. create an xml to run a restraint test from gitlab using https
2. run it using restraint
3.

Actual results:
fails with the following message:
ERROR: While connecting to /satellite5qe/RHN-Satellite.git: TLS support is not available

Expected results:
task is cloned and successfully run

Additional info:
driver running: RHEL 6.7
system under test: RHEL 6.6

Comment 1 Artem Savkov 2016-05-19 14:20:31 UTC

Even if https was supported (working on it) you wouldn't be able to use the url you specified, as it is an url for git-over-http(s) scheme which is not supported in restraint and probably won't be supported any time soon. What you should use instead is gitlab's/github's tarball capabilities, i.e. https://gitlab.cee.redhat.com/satellite5qe/RHN-Satellite/repository/archive.tar.gz?ref=master (still requires ssl though)

Comment 2 Artem Savkov 2016-11-07 09:36:08 UTC

The changes needed for https support are merged and should be available in next restraint release.

Comment 3 Dan Callaghan 2017-04-04 00:10:40 UTC

I think this was fixed by the switch to libcurl which went into restraint 0.1.28.

Comment 4 Dan Callaghan 2017-04-04 00:17:56 UTC

*** Bug 1391422 has been marked as a duplicate of this bug. ***