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):
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
"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.
Can view containers
Created attachment 1003854 [details]
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.