Bug #18217
openDocker registry sync does not use HTTP proxy configuration
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1333595
Description of problem:
Adding a new Docker registry on a katello inside a network that requires the use of a HTTP proxy to access the internet results in
Unable to log in to this Docker Registry - No route to host - connect(2) for "registry.access.redhat.com" port 443
Again, tcpdump is showing direct connect attempts to the upstream IP instead of using the proxy configured during installation.
Possibly related to BZ 1332395 for same issue with OSTree replication
Steps to Reproduce:
1. Configure katello to use http proxy, ensure that direct internet connection is not possible.
2. Create new Docker registry either via the WebUI or with
hammer docker registry create --name "Red Hat Openshift3" --url https://registry.access.redhat.com/openshift3
Actual results:
Could not create the registry:
Unable to log in to this Docker Registry - No route to host - connect(2) for "registry.access.redhat.com" port 443
Expected results:
Connection to registry succeeds via web proxy