Bug 1328550 - TLS error trying to clone gits using https from gitlab
Summary: TLS error trying to clone gits using https from gitlab
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Restraint
Classification: Retired
Component: general
Version: 0.1.24
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 0.1.28
Assignee: Artem Savkov
QA Contact: tools-bugs
URL:
Whiteboard:
: 1391422 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 15:57 UTC by Vimal Patel
Modified: 2017-04-04 00:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 09:36:08 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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. ***
Note You need to log in before you can comment on or make changes to this bug.