Bug 1375891
| Summary: | SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Alex Jia <ajia> |
| Component: | atomic | Assignee: | Brent Baude <bbaude> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | aweiteka, bbaude, dwalsh, gscrivan, lsm5, mitr |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 09:06: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: | |||
|
Comment 3
Brent Baude
2016-09-14 20:33:35 UTC
or perhaps is kept under a v1 schema? 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.) (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 > adding "--tls-verify=false" in skopeo solves this error.
Fascinating. But this is till a Python traceback.
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). 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 |