Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1433458 - DKR1008: Could not find registry API at https://docker-registry.engineering.redhat.com
DKR1008: Could not find registry API at https://docker-registry.engineering.r...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Pulp (Show other bugs)
6.2.6
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: Unused
Assigned To: satellite6-bugs
jcallaha
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-17 12:47 EDT by Tom McKay
Modified: 2018-09-19 11:09 EDT (History)
17 users (show)

See Also:
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: ---


Attachments (Terms of Use)
failed sync (52.16 KB, image/png)
2017-11-02 15:47 EDT, jcallaha
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Pulp Redmine 2643 Normal CLOSED - CURRENTRELEASE DKR1008: Could not find registry API at https://docker-registry.engineering.redhat.com 2017-04-27 10:03 EDT

  None (edit)
Description Tom McKay 2017-03-17 12:47:19 EDT
https://pulp.plan.io/issues/2643

Internal registry https://docker-registry.engineering.redhat.com cannot sync repos into foreman. 'docker pull' works

docker pull docker-registry.engineering.redhat.com/thomasmckay/freewill:v2
Packages:

[root@devel ~]# rpm -qa | grep pulp
pulp-server-2.12.0-1.el7.noarch
pulp-puppet-plugins-2.12.0-1.el7.noarch
pulp-selinux-2.12.0-1.el7.noarch
python-pulp-client-lib-2.12.0-1.el7.noarch
python-pulp-ostree-common-1.2.0-1.el7.noarch
pulp-client-1.0-1.noarch
python-pulp-docker-common-2.3.0-1.el7.noarch
pulp-docker-admin-extensions-2.3.0-1.el7.noarch
python-pulp-puppet-common-2.12.0-1.el7.noarch
python-pulp-oid_validation-2.12.0-1.el7.noarch
pulp-rpm-admin-extensions-2.12.0-1.el7.noarch
python-isodate-0.5.0-4.pulp.el7.noarch
python-kombu-3.0.33-6.pulp.el7.noarch
python-pulp-common-2.12.0-1.el7.noarch
python-pulp-rpm-common-2.12.0-1.el7.noarch
pulp-admin-client-2.12.0-1.el7.noarch
pulp-puppet-tools-2.12.0-1.el7.noarch
pulp-docker-plugins-2.3.0-1.el7.noarch
python-pulp-bindings-2.12.0-1.el7.noarch
pulp-ostree-plugins-1.2.0-1.el7.noarch
pulp-katello-1.0.2-1.el7.noarch
python-pulp-repoauth-2.12.0-1.el7.noarch
pulp-rpm-plugins-2.12.0-1.el7.noarch
python-pulp-streamer-2.12.0-1.el7.noarch
rubygem-smart_proxy_pulp-1.3.0-1.el7.noarch
Log:

Mar 17 15:36:30 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: Running task : [9337920c-83ba-454f-a9b4-8cfb79d8f478]
Mar 17 15:36:30 devel.example.com pulp[10325]: pulp_docker.plugins.importers.sync:DEBUG: v1 API skipped due to config
Mar 17 15:36:30 devel.example.com pulp[10325]: pulp_docker.plugins.registry:DEBUG: Determining if the registry URL can do v2 of the Docker API.
Mar 17 15:36:30 devel.example.com pulp[10325]: pulp_docker.plugins.registry:DEBUG: Retrieving https://docker-registry.engineering.redhat.com/v2/
Mar 17 15:36:30 devel.example.com pulp[10325]: nectar.downloaders.threaded:DEBUG: Attempting to connect to https://docker-registry.engineering.redhat.com/v2/.
Mar 17 15:36:30 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (1): docker-registry.engineering.redhat.com
Mar 17 15:36:30 devel.example.com pulp[10312]: celery.worker.job:INFO: Task pulp.server.async.tasks._queue_reserved_task[4d1f4ce3-c31c-44c6-8637-301bbb902a2a] succeeded in 0.0419807829894s: None
Mar 17 15:36:30 devel.example.com pulp[10180]: celery.worker.job:DEBUG: Task accepted: pulp.server.managers.repo.sync.sync[9337920c-83ba-454f-a9b4-8cfb79d8f478] pid:10325
Mar 17 15:36:30 devel.example.com pulp[10180]: celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._release_resource[2bff1f0d-b39c-435a-97b9-dff17929a209]
Mar 17 15:36:30 devel.example.com pulp[10456]: pulp.server.webservices.views.decorators:DEBUG: User preauthenticated: admin
Mar 17 15:36:31 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:DEBUG: "GET /v2/ HTTP/1.1" 401 87
Mar 17 15:36:31 devel.example.com pulp[10325]: nectar.downloaders.threaded:DEBUG: download failed: Download of https://docker-registry.engineering.redhat.com/v2/ failed with code 401: Unauthorized
Mar 17 15:36:31 devel.example.com pulp[10325]: pulp_docker.plugins.registry:DEBUG: Download unauthorized, attempting to retrieve a token.
Mar 17 15:36:31 devel.example.com pulp[10325]: pulp_docker.plugins.token_util:DEBUG: Requesting token from https://docker-registry.engineering.redhat.com/openshift/token
Mar 17 15:36:31 devel.example.com pulp[10325]: nectar.downloaders.threaded:DEBUG: Attempting to connect to https://docker-registry.engineering.redhat.com/openshift/token.
Mar 17 15:36:31 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (1): docker-registry.engineering.redhat.com
Mar 17 15:36:31 devel.example.com pulp[10456]: pulp.server.webservices.views.decorators:DEBUG: User preauthenticated: admin
Mar 17 15:36:31 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:DEBUG: "GET /openshift/token HTTP/1.1" 200 49
Mar 17 15:36:31 devel.example.com pulp[10325]: nectar.downloaders.threaded:DEBUG: Attempting to connect to https://docker-registry.engineering.redhat.com/v2/.
Mar 17 15:36:31 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (2): docker-registry.engineering.redhat.com
Mar 17 15:36:31 devel.example.com pulp[10456]: pulp.server.webservices.views.decorators:DEBUG: User preauthenticated: admin
Mar 17 15:36:32 devel.example.com pulp[10325]: requests.packages.urllib3.connectionpool:DEBUG: "GET /v2/ HTTP/1.1" 401 87
Mar 17 15:36:32 devel.example.com pulp[10325]: nectar.downloaders.threaded:DEBUG: download failed: Download of https://docker-registry.engineering.redhat.com/v2/ failed with code 401: Unauthorized
Mar 17 15:36:32 devel.example.com pulp[10459]: pulp.server.webservices.views.decorators:DEBUG: User preauthenticated: admin
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:INFO: Task failed : [9337920c-83ba-454f-a9b4-8cfb79d8f478] : Could not find registry API at https://docker-registry.engineering.redhat.com
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296) Traceback (most recent call last):
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 240, in trace_task
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     R = retval = fun(*args, **kwargs)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 505, in __call__
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     return super(Task, self).__call__(*args, **kwargs)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 108, in __call__
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     return super(PulpTask, self).__call__(*args, **kwargs)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 437, in __protected_call__
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     return self.run(*args, **kwargs)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 762, in sync
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     sync_report = sync_repo(transfer_repo, conduit, call_config)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 708, in wrap_f
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     return f(*args, **kwargs)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp_docker/plugins/importers/importer.py", line 83, in sync_repo
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     self.sync_step = sync.SyncStep(repo=repo, conduit=sync_conduit, config=config)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)   File "/usr/lib/python2.7/site-packages/pulp_docker/plugins/importers/sync.py", line 89, in __init__
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)     raise PulpCodedException(error_code=error_codes.DKR1008, registry=url)
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296) PulpCodedException: Could not find registry API at https://docker-registry.engineering.redhat.com
Mar 17 15:36:32 devel.example.com pulp[10325]: pulp.server.async.tasks:DEBUG: (10325-43296)
Comment 3 Tom McKay 2017-03-17 22:22:34 EDT
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
Comment 4 Tom McKay 2017-03-17 22:31:04 EDT
From what I understand, the atomic-registry is using GoogleAuthProvider while docker-registry is using LDAPPasswordIdentityProvider.
Comment 5 Luiz Carvalho 2017-03-20 11:17:35 EDT
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
Comment 6 Tom McKay 2017-03-20 13:46:07 EDT
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
Comment 7 pulp-infra@redhat.com 2017-03-21 15:17:51 EDT
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2017-03-21 15:17:56 EDT
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 9 Ina Panova 2017-03-22 10:27:37 EDT
more info about this issue https://pulp.plan.io/issues/2643#note-4 and https://pulp.plan.io/issues/2643#note-5
Comment 10 pulp-infra@redhat.com 2017-03-23 09:32:08 EDT
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 11 Brian Bouterse 2017-04-11 14:05:25 EDT
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 12 pulp-infra@redhat.com 2017-04-11 14:20:22 EDT
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 13 pulp-infra@redhat.com 2017-04-17 09:32:54 EDT
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 14 pulp-infra@redhat.com 2017-04-27 10:03:47 EDT
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 16 Ashfaqur Rahaman 2017-08-07 21:19:27 EDT
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
Comment 21 jcallaha 2017-11-02 15:47:16 EDT
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
Comment 22 jcallaha 2017-11-02 15:47 EDT
Created attachment 1347110 [details]
failed sync
Comment 23 pulp-infra@redhat.com 2017-11-02 16:03:00 EDT
Requesting needsinfo from upstream developer ipanova@redhat.com because the 'FailedQA' flag is set.
Comment 26 jcallaha 2017-11-03 11:07:40 EDT
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.
Comment 27 Bryan Kearney 2018-02-21 12:34:24 EST
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
Comment 28 Bryan Kearney 2018-02-21 12:34:26 EST
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

Note You need to log in before you can comment on or make changes to this bug.