Bug 1310443 - Testing a connection to docker resource throws 400lines backtrace to /var/log/httpd/error_log
Summary: Testing a connection to docker resource throws 400lines backtrace to /var/log...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.1.6
Hardware: x86_64
OS: Linux
medium
medium vote
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-21 16:06 UTC by Pavel Moravec
Modified: 2021-08-30 10:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-04 13:19:10 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2184801 0 None None None 2017-08-07 18:44:14 UTC

Description Pavel Moravec 2016-02-21 16:06:40 UTC
Description of problem:
Having a docker compute resource, regardless how correctly / wrongly configured, clicking to "Test connection" button generates huge backtrace to /var/log/httpd/error_log .

It might be a red herring, but still..


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


How reproducible:
100%


Steps to Reproduce:
1. Create a compute resource of type docker
2. Put whatever to URL (try with valid and also invalid URL)
3. Click to "Test Connection"
4. Observe /var/log/httpd/error_log


Actual results:
/var/log/httpd/error_log gets populated with:

[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] [excon][WARNING] Invalid Excon connection keys: :username
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/excon-0.38.0/lib/excon/connection.rb:393:in `validate_params'
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/excon-0.38.0/lib/excon/connection.rb:57:in `initialize'
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/excon-0.38.0/lib/excon.rb:148:in `new'
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/excon-0.38.0/lib/excon.rb:148:in `new'
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/docker-api-1.17.0/lib/docker/connection.rb:32:in `resource'
[ 2016-02-21 17:05:29.1366 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/docker-api-1.17.0/lib/docker/connection.rb:44:in `request'
[ 2016-02-21 17:05:29.1367 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/docker-api-1.17.0/lib/docker/connection.rb:59:in `block (2 levels) in <class:Connection>'
[ 2016-02-21 17:05:29.1367 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/docker-api-1.17.0/lib/docker.rb:94:in `version'
[ 2016-02-21 17:05:29.1367 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.24/app/models/foreman_docker/docker.rb:110:in `api_version'
[ 2016-02-21 17:05:29.1367 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.24/app/models/foreman_docker/docker.rb:119:in `test_connection'
[ 2016-02-21 17:05:29.1367 1858/7f13c22bc700 Pool2/Implementation.cpp:1274 ]: [App 1960 stderr] /usr/share/foreman/app/controllers/compute_resources_controller.rb:97:in `test_connection'
..


Expected results:
no such error


Additional info:

Comment 2 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2016-07-26 15:35:35 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 5 Bryan Kearney 2017-08-04 13:19:10 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.