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:

When creating a docker repository, the UI will provide the user with an example for the 'URL' to dockerhub.  Unfortunately, the URL previously used is no longer valid; therefore, we need to update it to a URL that currently works.

Version-Release number of selected component (if applicable):
Satellite 6.2 early snap

How reproducible:
Always

Steps to Reproduce:
1. go to Content -> Products
2. create a product via 'New Product'
3. click 'Create Repository'
4. select Type 'docker'

Actual results:

Observe text under URL indicating:
URL of the registry you want to sync. Example: https://registry.hub.docker.com

Expected results:

Change the URL to be:

https://registry-1.docker.io

Additional info:

It is quite possible that the URL for accessing dockerhub content will change again; however, this update will put it to current working URL and is based upon feedback from the pulp team.

Created redmine issue http://projects.theforeman.org/issues/13992 from this bug

Moving to POST since upstream bug http://projects.theforeman.org/issues/13992 has been closed
-------------
Zach Huntington-Meath
Applied in changeset commit:katello|e898a835b35dae8585b6843b0302532ac5eabe8b.

Verified that the help text for URL when creating a docker repository now states the following:

"URL of the registry you want to sync. Example: https://registry-1.docker.io/"

If this URL is used and a valid upstream docker name is used, content can be synced form dockerhub.

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-2016:1500