Bug #18217

Docker registry sync does not use HTTP proxy configuration

Added by Thomas McKay over 1 year ago. Updated 8 days ago.

Status:Ready For Testing
Priority:Normal
Assignee:Sebastian Gräßl
Category:-
Target version:Katello - Katello Backlog
Difficulty: Team Backlog:
Triaged: Fixed in Releases:
Bugzilla link:1333595 Found in Releases:
Pull request:https://github.com/theforeman/foreman-docker/pull/189

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

History

#1 Updated by Thomas McKay over 1 year ago

  • Subject changed from Docker registry sync does not use HTTP proxy configuration to Docker registry sync does not use HTTP proxy configuration
  • Target version set to 161

#2 Updated by Thomas McKay over 1 year ago

  • Assignee changed from Thomas McKay to Partha Aji

#3 Updated by Justin Sherrill over 1 year ago

  • Legacy Backlogs Release (now unused) set to 114

#4 Updated by Thomas McKay over 1 year ago

  • Project changed from Katello to Docker
  • Category deleted (Docker)
  • Target version changed from 161 to 117

This is a case where the foreman-docker plugin is not using configured proxy. Unrelated to katello content sync via pulp. Moving to appropriate project.

#5 Updated by Thomas McKay over 1 year ago

  • Assignee deleted (Partha Aji)

#6 Updated by Sebastian Gräßl over 1 year ago

  • Assignee set to Sebastian Gräßl

#7 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-docker/pull/189 added

#8 Updated by Marek Hulán 12 months ago

  • Target version changed from 117 to 1.17.0-RC2

#9 Updated by Marek Hulán 11 months ago

  • Target version changed from 1.17.0-RC2 to 1.18.0-RC2

#10 Updated by Marek Hulán 11 months ago

  • Target version changed from 1.18.0-RC2 to 214

#11 Updated by Marek Hulán 10 months ago

  • Target version changed from 214 to 1.16.0-RC2

#12 Updated by Marek Hulán 9 months ago

  • Target version changed from 1.16.0-RC2 to 1.16.0-RC1

#13 Updated by Marek Hulán 9 months ago

  • Target version changed from 1.16.0-RC1 to 1.16.2

#14 Updated by Marek Hulán 8 months ago

  • Target version changed from 1.16.2 to 1.16.1

#15 Updated by Marek Hulán 7 months ago

  • Target version changed from 1.16.1 to 238

Also available in: Atom PDF