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:
Unable to create Container from katello synced docker repos

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150205.0

How reproducible:
Always

Steps to Reproduce:
1. Create a custom product with docker repos, sync it
2. Navigate to Containers -> New Container page
3. Select a Docker Compute resource -> Click Next

Actual results:
Under Image tab -> I see 'Docker Hub', 'External Registry'

Expected results:
'Katello' is missing


Additional info:

Moving to POST since upstream bug http://projects.theforeman.org/issues/8918 has been closed
-------------
Partha Aji
Applied in changeset commit:katello|cdbebe9d90a449e6f8cfd0bc058f6cc95e8a1a1a.

Verified on: Satellite-6.1.0-RHEL-7-20150303.0 and Satellite-6.1.0-RHEL-6-20150303.0

Steps to verify:

1. Create a Docker-based compute resource pointing to http://localhost:2375
2. Created a Product with a Docker repository and synced the repo.
3. On New Container wizard:
   Selected the Compute Resource
   In next step, selected the repository
   Finished the wizard by creating a container running top command and enabled PTY
4. The container was created and was able to start it and read its logs.

This bug is slated to be released with Satellite 6.1.

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-2015:1592