Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
While trying to sync google container registry from satellie 6.3 GUI, we get following error:
Output
Could not find registry API at https://gcr.io
Errors:
DKR1008: Could not find registry API at https://gcr.io
Version-Release number of selected component (if applicable):
Satellite 6.3
How reproducible:
Satellite GUI > Content > Product > Repository > Sync Now
~~~
Type Docker
Registry URL https://gcr.io
Upstream Repository Name google_containers/kube-controller-manager-amd64
~~~
Actual results:
Fails to sync
---
pulp_tasks:
- exception:
task_type: pulp.server.managers.repo.sync.sync
_href: "/pulp/api/v2/tasks/01144bec-41ed-46aa-ab5a-1d034cb814c7/"
task_id: 01144bec-41ed-46aa-ab5a-1d034cb814c7
tags:
- pulp:repository:19b81bf6-5fe8-4f53-8a6c-82f92d6efb93
- pulp:action:sync
finish_time: '2018-03-14T04:46:46Z'
_ns: task_status
start_time: '2018-03-14T04:46:35Z'
traceback: |
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 240, in trace_task
R = retval = fun(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 527, in __call__
return super(Task, self).__call__(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 107, in __call__
return super(PulpTask, self).__call__(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 438, in __protected_call__
return self.run(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 769, in sync
sync_report = sync_repo(transfer_repo, conduit, call_config)
File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 730, in wrap_f
return f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pulp_docker/plugins/importers/importer.py", line 83, in sync_repo
self.sync_step = sync.SyncStep(repo=repo, conduit=sync_conduit, config=config)
File "/usr/lib/python2.7/site-packages/pulp_docker/plugins/importers/sync.py", line 89, in __init__
raise PulpCodedException(error_code=error_codes.DKR1008, registry=url)
PulpCodedException: Could not find registry API at https://gcr.io
Expected results:
google container registry should be synced similar to docker or redhat public registry.
Additional info:
--Docker registry to sync--
gcr.io/google_containers/kube-apiserver-amd64 v1.5.1
gcr.io/google_containers/kube-controller-manager-amd64 v1.5.1
gcr.io/google_containers/kube-proxy-amd64 v1.5.1
gcr.io/google_containers/kube-scheduler-amd64 v1.5.1
gcr.io/google_containers/kubernetes-dashboard-amd64 v1.5.0
gcr.io/google_containers/etcd-amd64 3.0.14-kubeadm
Comment 7pulp-infra@redhat.com
2018-04-17 13:02:23 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 8pulp-infra@redhat.com
2018-04-17 13:02:26 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2018-04-17 15:02:06 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 10pulp-infra@redhat.com
2018-04-17 16:32:03 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 11pulp-infra@redhat.com
2018-04-18 14:33:56 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 13pulp-infra@redhat.com
2018-04-20 10:32:19 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 14pulp-infra@redhat.com
2018-04-20 11:01:59 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 17sthirugn@redhat.com
2018-05-09 16:17:16 UTC
=== HOTFIX INSTRUCTIONS FOR SATELLITE 6.3.1 ONLY ===
1. Download attached file hotfix-1555165.tar.gz
2. Extract the tarball and install the required packages in Satellite
3. Restart service on Satellite
katello-service restart
Comment 18sthirugn@redhat.com
2018-05-09 16:17:51 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://access.redhat.com/errata/RHBA-2018:1950
Comment 28pulp-infra@redhat.com
2018-07-09 14:09:10 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 29pulp-infra@redhat.com
2018-07-09 15:06:37 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.