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.
Bug 1194204 - Unable to register discovered host via https proxy
Summary: Unable to register discovered host via https proxy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1193977
TreeView+ depends on / blocked
 
Reported: 2015-02-19 10:41 UTC by Sachin Ghai
Modified: 2017-02-23 20:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:25:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
we can register the host via https proxy (33.06 KB, image/png)
2015-04-02 13:01 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9459 0 Normal Closed Unable to register discovered host via https proxy 2020-09-15 07:35:35 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Sachin Ghai 2015-02-19 10:41:27 UTC 
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:
Comment 1 Lukas Zapletal 2015-02-19 13:56:19 UTC 
Fix awaiting review upstream.
Comment 5 Sachin Ghai 2015-02-26 11:04:55 UTC 
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
--
Comment 9 Sachin Ghai 2015-03-13 12:02:46 UTC 
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 ?
Comment 10 Lukas Zapletal 2015-03-13 12:18:29 UTC 
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.
Comment 11 Sachin Ghai 2015-03-13 15:16:17 UTC 
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.
Comment 12 Sachin Ghai 2015-03-13 15:18:31 UTC 
Moving to assigned state as per comment 10 and 11. Please make the appropriate change so that mart_proxy_discovery package installed automatically.
Comment 16 Sachin Ghai 2015-04-02 13:00:14 UTC 
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.
Comment 17 Sachin Ghai 2015-04-02 13:01:36 UTC 
Created attachment 1010155 [details]
we can register the host via https proxy
Comment 18 Bryan Kearney 2015-08-11 13:19:02 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 19 errata-xmlrpc 2015-08-12 05:25:16 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.