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:
Satellite 6 is not able to sync private registry hosted on Docker Hub.

Version-Release number of selected component (if applicable):


How reproducible:
Allways

Steps to Reproduce:
1. Create a registry on https://hub.docker.com
2. Push an image in the registry and make the registry private
3. Create the Docker type repository in the Satellite pointing to the private registry
4. Try to sync the repository

Actual results:
Sync fails with following error:
Could not fetch repository username/registry from registry https://registry.hub.docker.com - Unauthorized or Not Found

Expected results:
Registry is synced.

Additional info:
- Registry entry in Containers > Registries is created and credentials are correct.
- If the registry is not set as Private, sync is working without any issues
- Pulling from the private registry works

Support for authentication to a registry was added to Pulp 2.10.0 here:

https://pulp.plan.io/issues/1291

Partha, can you confirm:

1) Does sat 6.2 include this feature? The Pulp change would need to have been backported. Katello would of course need to facilitate setting the username and password.

2) Has this been tested against docker hub? Or private registries? Or anything else?

Connecting redmine issue http://projects.theforeman.org/issues/16481 from this bug

Changes upstream for quite some time.

Verified both upstream and downstream 6.4 snap 3

Removed the needinfo as BZ is verified

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:2927