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 1463371 - Satellite 6: Compute Resource setup does not honor proxy settings, connecting directly instead.
Summary: Satellite 6: Compute Resource setup does not honor proxy settings, connecting...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.2.8
Hardware: All
OS: Linux
high
high
Target Milestone: 6.4.0
Assignee: Justin Sherrill
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-20 16:32 UTC by Rodrigo A B Freire
Modified: 2022-03-13 14:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:16:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Sat64 now supports EC2 CR addition via the HTTP Proxy (74.77 KB, image/png)
2018-07-05 14:04 UTC, Kedar Bidarkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12216 0 'Normal' 'Closed' 'allow compute resource connections to use a proxy' 2019-11-12 18:52:06 UTC
Red Hat Knowledge Base (Solution) 3087801 0 None None None 2017-06-20 16:33:35 UTC

Description Rodrigo A B Freire 2017-06-20 16:32:32 UTC 
Description of problem:
When defining a AWS Compute Resource, Satellite Server does not use the local proxy configuration. It tries a direct connection instead.

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

How reproducible:
100% / Always

Steps to Reproduce:
1. Configure Satellite to use a Proxy Server
2. Define a AWS Compute Resource
3. Save the AWS settings

Actual results:
The AWS EC2 compute setup fails. It tries a direct connection to its real IP address.

Expected results:
Satellite should honour and divert the traffic through the configured and designated Proxy Server.

Additional info:
The proxy configuration was defined and configured as per Solution https://access.redhat.com/solutions/1455813.
Comment 2 Satellite Program 2017-06-23 02:18:32 UTC 
Upstream bug assigned to jsherril
Comment 3 Satellite Program 2017-06-23 02:18:36 UTC 
Upstream bug assigned to jsherril
Comment 4 Satellite Program 2017-10-12 16:20:55 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/12216 has been resolved.
Comment 5 Kedar Bidarkar 2018-07-05 14:01:12 UTC 
Tested this successfully and this works with Sat6.4.0-snap9

1530798582.517   1144 <IP-Address> TCP_TUNNEL/200 8039 CONNECT ec2.ap-south-1.amazonaws.com:443 admin HIER_DIRECT/52.95.88.14 - [Proxy-Authorization: Basic YWRtaW46cmVkaGF0\r\nProxy-Connection: Keep-Alive\r\nHost: ec2.ap-south-1.amazonaws.com:443\r\n] []
1530798594.975    969 <IP-Address> TCP_TUNNEL/200 8039 CONNECT ec2.ap-south-1.amazonaws.com:443 admin HIER_DIRECT/52.95.88.14 - [Proxy-Authorization: Basic YWRtaW46cmVkaGF0\r\nProxy-Connection: Keep-Alive\r\nHost: ec2.ap-south-1.amazonaws.com:443\r\n] []
1530798616.753    971 <IP-Address> TCP_TUNNEL/200 8039 CONNECT ec2.ap-south-1.amazonaws.com:443 admin HIER_DIRECT/52.95.88.14 - [Proxy-Authorization: Basic YWRtaW46cmVkaGF0\r\nProxy-Connection: Keep-Alive\r\nHost: ec2.ap-south-1.amazonaws.com:443\r\n] []


Below are the steps followed.

1) Create a new proxy "sat6_proxy" via, Infrastructure --> HTTP Capsules --> NEW HTTP Proxy  
2) Provide all the details related to the HTTP proxy, user@password, port, proxy_hostname and so on.
3) From Compute Resource page, while adding EC2 CR, specify "sat6_proxy" as the HTTP_PROXY.


Will be attaching a screenshot shortly.
Comment 6 Kedar Bidarkar 2018-07-05 14:04:21 UTC 
Created attachment 1456780 [details]
Sat64 now supports EC2 CR addition via the HTTP Proxy
Comment 7 Bryan Kearney 2018-10-16 19:16:04 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-2018:2927
Note You need to log in before you can comment on or make changes to this bug.