Project

General

Profile

Actions

Bug #18217

open

Docker registry sync does not use HTTP proxy configuration

Added by Thomas McKay over 7 years ago. Updated over 5 years ago.

Status:
Ready For Testing
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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

Actions

Also available in: Atom PDF