Red Hat Bugzilla – Bug 1463371
Satellite 6: Compute Resource setup does not honor proxy settings, connecting directly instead.
Last modified: 2017-10-12 12:20:55 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):
100% / Always
Steps to Reproduce:
1. Configure Satellite to use a Proxy Server
2. Define a AWS Compute Resource
3. Save the AWS settings
The AWS EC2 compute setup fails. It tries a direct connection to its real IP address.
Satellite should honour and divert the traffic through the configured and designated Proxy Server.
The proxy configuration was defined and configured as per Solution https://access.redhat.com/solutions/1455813.
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/12216 has been resolved.