Bug 1433458
| Summary: | DKR1008: Could not find registry API at https://docker-registry.engineering.redhat.com | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Tom McKay <tomckay> | ||||
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.2.6 | CC: | adahms, arahaman, bbuckingham, bkearney, bmbouter, daviddavis, dkliban, ehelms, ggainey, ipanova, jcallaha, lucarval, mhrivnak, oshtaier, paji, pcreech, rchan, satellite6-bugs, ttereshc | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pulp-2.13.0 | Doc Type: | Release Note | ||||
| Doc Text: |
To synchronize container images from a registry with self-signed certificates, you must either configure certificates manually or disable the SSL Verify option.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: | |||||||
| Attachments: |
|
||||||
|
Description
Tom McKay
2017-03-17 16:47:19 UTC
Looks identical except for the dates, could that be an issue? $ curl -k -I https://docker-registry.engineering.redhat.com/v2 HTTP/2.0 301 docker-distribution-api-version:registry/2.0 location:/v2/ content-type:text/plain; charset=utf-8 date:Fri, 17 Mar 2017 22:38:30 GMT $ curl -k -I https://docker-registry.engineering.redhat.com/v2/ HTTP/2.0 401 content-type:application/json; charset=utf-8 docker-distribution-api-version:registry/2.0 www-authenticate:Bearer realm="https://docker-registry.engineering.redhat.com/openshift/token" content-length:87 date:Fri, 17 Mar 2017 22:38:38 GMT $ curl -k -I https://atomic-registry.usersys.redhat.com:5000/v2 HTTP/2.0 301 docker-distribution-api-version:registry/2.0 location:/v2/ content-type:text/plain; charset=utf-8 date:Sat, 18 Mar 2017 02:17:41 GMT $ curl -k -I https://atomic-registry.usersys.redhat.com:5000/v2/ HTTP/2.0 401 content-type:application/json; charset=utf-8 docker-distribution-api-version:registry/2.0 www-authenticate:Bearer realm="https://atomic-registry.usersys.redhat.com:5000/openshift/token" x-registry-supports-signatures:1 content-length:87 date:Sat, 18 Mar 2017 02:17:47 GMT From what I understand, the atomic-registry is using GoogleAuthProvider while docker-registry is using LDAPPasswordIdentityProvider. I don't see a discrepancy with the dates: $ curl -k -I https://atomic-registry.usersys.redhat.com:5000/v2/ HTTP/2 401 content-type: application/json; charset=utf-8 docker-distribution-api-version: registry/2.0 www-authenticate: Bearer realm="https://atomic-registry.usersys.redhat.com:5000/openshift/token" x-registry-supports-signatures: 1 content-length: 87 date: Mon, 20 Mar 2017 15:14:05 GMT $ curl -k -I https://docker-registry.engineering.redhat.com/v2/ HTTP/2 401 content-type: application/json; charset=utf-8 docker-distribution-api-version: registry/2.0 www-authenticate: Bearer realm="https://docker-registry.engineering.redhat.com/openshift/token" content-length: 87 date: Mon, 20 Mar 2017 15:14:19 GMT Although I do see that atomic-registry returns the addtional header: x-registry-supports-signatures:1 From @ipanova --- failure --- [ipanova@ipanova ~]$ curl -k -I -L -H 'Authorization: Bearer anonymous' https://atomic-registry.usersys.redhat.com:5000/v2/ HTTP/1.1 200 OK Content-Length: 2 Content-Type: application/json; charset=utf-8 Docker-Distribution-Api-Version: registry/2.0 X-Registry-Supports-Signatures: 1 Date: Mon, 20 Mar 2017 17:30:52 GMT [ipanova@ipanova ~]$ curl -k -I -L -H 'Authorization: Bearer anonymous' https://docker-registry.engineering.redhat.com/v2 HTTP/1.1 301 Moved Permanently Docker-Distribution-Api-Version: registry/2.0 Location: /v2/ Date: Mon, 20 Mar 2017 17:31:18 GMT Content-Type: text/plain; charset=utf-8 HTTP/1.1 401 Unauthorized Content-Type: application/json; charset=utf-8 Docker-Distribution-Api-Version: registry/2.0 Www-Authenticate: Basic realm=openshift,error="access denied" Date: Mon, 20 Mar 2017 17:31:18 GMT Content-Length: 87 --- failure --- $ curl -k -I -L -H 'Authorization: Bearer ...snipped token...' https://registry-1.docker.io/v2 HTTP/1.1 301 Moved Permanently Docker-Distribution-Api-Version: registry/2.0 Location: /v2/ Date: Mon, 20 Mar 2017 17:34:24 GMT Content-Type: text/plain; charset=utf-8 Strict-Transport-Security: max-age=31536000 HTTP/1.1 200 OK Content-Length: 2 Content-Type: application/json; charset=utf-8 Docker-Distribution-Api-Version: registry/2.0 Date: Mon, 20 Mar 2017 17:34:24 GMT Strict-Transport-Security: max-age=31536000 The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. more info about this issue https://pulp.plan.io/issues/2643#note-4 and https://pulp.plan.io/issues/2643#note-5 The Pulp upstream bug status is at POST. Updating the external tracker on this bug. The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. Hello, Is there any work around in pulp-docker-plugins-2.0.3-1 version ? Satellite version : 6.2.8 We are facing issue while syncing docker repo : https://docker.io ************************ Error: Katello::Errors::PulpError DKR1008: Could not find registry API at https://docker.io ************************ Thanks Ash Failed QA in Satellite 6.3 Beta Snap 22. Still seeing the issue persisting as initially reported. See attached screenshot and below pulp-admin session. pulp docker repo create --feed=https://docker-registry.engineering.redhat.com --upstream-name=thomasmckay/freewill --repo-id=eric Repository [eric] successfully created [vagrant@obelix ~]$ pulp docker repo sync run --repo-id=eric +----------------------------------------------------------------------+ Synchronizing Repository [eric] +----------------------------------------------------------------------+ This command may be exited via ctrl+c without affecting the request. Task Failed Could not find registry API at https://docker-registry.engineering.redhat.com Created attachment 1347110 [details]
failed sync
Requesting needsinfo from upstream developer ipanova because the 'FailedQA' flag is set. Verified in Satellite 6.3 Snap 22. Re-tested after changing the SSL Verify field to No. The repo was successfully synced without any of the previously seen issues. See attached screenshot for verification. 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://access.redhat.com/errata/RHSA-2018:0336 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://access.redhat.com/errata/RHSA-2018:0336 |