Bug 1463371 - Satellite 6: Compute Resource setup does not honor proxy settings, connecting directly instead.
Satellite 6: Compute Resource setup does not honor proxy settings, connecting...
Status: ON_QA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Infrastructure (Show other bugs)
All Linux
high Severity high (vote)
: Beta
: --
Assigned To: Justin Sherrill
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-06-20 12:32 EDT by Rodrigo A B Freire
Modified: 2018-05-17 01:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 12216 None None None 2017-06-20 12:32 EDT
Red Hat Knowledge Base (Solution) 3087801 None None None 2017-06-20 12:33 EDT

  None (edit)
Description Rodrigo A B Freire 2017-06-20 12:32:32 EDT
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 pm-sat@redhat.com 2017-06-22 22:18:32 EDT
Upstream bug assigned to jsherril@redhat.com
Comment 3 pm-sat@redhat.com 2017-06-22 22:18:36 EDT
Upstream bug assigned to jsherril@redhat.com
Comment 4 pm-sat@redhat.com 2017-10-12 12:20:55 EDT
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/12216 has been resolved.

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