Bug 1463371

Summary: Satellite 6: Compute Resource setup does not honor proxy settings, connecting directly instead.
Product: Red Hat Satellite Reporter: Rodrigo A B Freire <rfreire>
Component: InfrastructureAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.8CC: jcallaha, kbidarka, timello, wpinheir
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
URL: http://projects.theforeman.org/issues/12216
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:16:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Sat64 now supports EC2 CR addition via the HTTP Proxy none

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