RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1375891 - SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol
Summary: SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-14 07:54 UTC by Alex Jia
Modified: 2016-11-04 09:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 09:06:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2628 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-11-03 18:17:14 UTC

Comment 3 Brent Baude 2016-09-14 20:33:35 UTC 
Alex,

When I replicate and debug your signing action, it appears like the image in question is protected with authentication.  Is that correct?
Comment 4 Brent Baude 2016-09-14 20:42:05 UTC 
or perhaps is kept under a v1 schema?
Comment 7 Miloslav Trmač 2016-09-15 16:26:16 UTC 
check_v1_registry → requests.get(v1_url); what is the v1_url here?

Wild guess would be that this is an attempt to connect to a HTTP (non-TLS) server using HTTPS.

(And I can’t see any connection to skopeo.)
Comment 8 Antonio Murdaca 2016-09-15 16:33:08 UTC 
(In reply to Miloslav Trmač from comment #7)
> check_v1_registry → requests.get(v1_url); what is the v1_url here?
> 
> Wild guess would be that this is an attempt to connect to a HTTP (non-TLS)
> server using HTTPS.
> 
> (And I can’t see any connection to skopeo.)

discussing about this with Brent, adding "--tls-verify=false" in skopeo solves this error.

Still discussing with Brent on the best approach to silence/prompt this error in the atomic CLI
Comment 9 Miloslav Trmač 2016-09-15 16:35:48 UTC 
> adding "--tls-verify=false" in skopeo solves this error.

Fascinating. But this is till a Python traceback.
Comment 10 Brent Baude 2016-09-15 22:11:35 UTC 
Based on feedback and discussions, this has a proposed fix ->https://github.com/projectatomic/atomic/pull/621.

In short, agreement with Miloslav and Antonio to use --tls-verify=false until we can accurately get the list of insecure registries from the docker configuration (including dealing with CIDR notation).
Comment 15 errata-xmlrpc 2016-11-04 09:06:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2628.html
Note You need to log in before you can comment on or make changes to this bug.