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:
New compute resource Test Connection does not work

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

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Containers -> New Container
2. Enter all valid details for a Docker container
3. Click 'Test Connection'


Actual results:
Nothing happened

Expected results:
Feedback saying if the connection succeeded or failed

Additional info:

Created attachment 989005 [details]
foreman-debug

*** This bug has been marked as a duplicate of bug 1052298 ***