Red Hat Bugzilla – Bug 1194204
Unable to register discovered host via https proxy
Last modified: 2017-02-23 15:28:37 EST
Description of problem: I ran the discovery via https proxy and while registering the host with server, I got following error: --- [2015-02-19T15:37:45.309389 #914] ERROR -- : Unable to resolve hostname for connecting client - 192.168.100.34. If it's to be a trusted host, ensure it has a reverse DNS entry. no name for 192.168.100.34 192.168.100.34 - - [19/Feb/2015 15:37:45] "POST /discovery/create HTTP/1.1" 403 159 0.0256 E, [2015-02-19T15:38:15.854556 #914] ERROR -- : Unable to resolve hostname for connecting client - 192.168.100.34. If it's to be a trusted host, ensure it has a reverse DNS entry. -- Version-Release number of selected component (if applicable): sat6.1 beta snap3 Satellite-6.1.0-RHEL-6-20150217.0 How reproducible: always Steps to Reproduce: 1. discover the host via https proxy 2. 3. Actual results: Unable to register discovered host via https proxy Expected results: Host should be successfully discovered and registered with sat6 server Additional info:
Fix awaiting review upstream.
Verified with sat6.1 beta snap4 Satellite-6.1.0-RHEL-6-20150224.0 I can discover host via proxy and it returns 200 in proxy.log -- 192.168.100.13 - - [26/Feb/2015 10:56:05] "POST /discovery/create HTTP/1.1" 200 - 0.8850 192.168.100.15 - - [26/Feb/2015 11:03:24] "POST /discovery/create HTTP/1.1" 200 - 0.5615 --
Installed sat6.1 beta snap6 compose2 (Satellite-6.1.0-RHEL-6-20150311.1). When I installed discovery smart_proxy package, I didn't restart the foreman-proxy service and discovery got failed with 404 error. But when I restarted the foreman-proxy service on sat6 server, discovery succeed. So not sure what changes we have made as per comment 6 ? Is it expected that user has to restart the service after installing proxy package ?
The smart_proxy_discovery package is expected to be installed by default, thus no manual installation and restart is needed. If it was not installed by default in the latest compose, then it failed QA I guess.
I Think it was discused earlier that foreman discovery plugin will be auto installed but smart_proxy_plugin will be installed manually. If this requirement is changed now and both needs to be installed automatically then its not working as per new requirement with recent snap. User still needs to install smart_proxy_discovery package manually and need to restart the foreman-proxy service.
Moving to assigned state as per comment 10 and 11. Please make the appropriate change so that mart_proxy_discovery package installed automatically.
Verified with snap9(Satellite-6.1.0-RHEL-6-20150331.1). Now foreman discovery plugin and smart_proxy package installed automatically via installer. And we can register the discovered host via https proxy.
Created attachment 1010155 [details] we can register the host via https proxy
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