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:
After user has connected a container compute resource and tries to view containers, an error is thrown.

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

Satellite-6.1.0-RHEL-7-20150311.1

How reproducible:
Seems to happen for me every time but I am not sure why others aren't seeing it.

Steps to Reproduce:
1.  Set up a container instance -- 
  Give it a Name, i.e., 'sesame'
  Give it an URL, i.e., 'http://sesame.example.com:5000'
2.  Go to Containers > All Containers


Actual results:


"Oops, we're sorry but something went wrong
 
×
Expected([200, 201, 202, 203, 204, 304]) <=> Actual(404 Not Found)
If you feel this is an error with Satellite 6 itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.

Back"


Expected results:

Can view containers

Additional info:

Created attachment 1003854 [details]
logs

This apparently comes from using the wrong port -- using the registry port (5000) instead of the daemon port (2375)

I should note that "Test Connection" did nothing, so there are two bz here:

* Test Connection should actually work
* We should handle bad ports gracefully.

Verified by QE on Satellite-6.1.0-RHEL-7-20150320.1. Test Connection button will now display an error message to the user.

This bug is slated to be released with Satellite 6.1.

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.