Bug #18217

Docker registry sync does not use HTTP proxy configuration

Added by Thomas McKay over 1 year ago. Updated 5 months ago.

Status:Ready For Testing
Priority:Normal
Assigned To:Sebastian Gräßl
Category:-
Target version:Foreman - Team Marek Iteration 25
Difficulty: Pull request:https://github.com/theforeman/foreman-docker/pull/189
Bugzilla link:1333595

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 Team Tom - iteration 10

#2 Updated by Thomas McKay over 1 year ago

  • Assigned To changed from Thomas McKay to Partha Aji

#3 Updated by Justin Sherrill over 1 year ago

  • Release set to Katello Backlog

#4 Updated by Thomas McKay over 1 year ago

  • Project changed from Katello to Docker
  • Category deleted (Docker)
  • Target version changed from Team Tom - iteration 10 to Team Daniel backlog

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

  • Assigned To deleted (Partha Aji)

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

  • Assigned To set to Sebastian Gräßl

#7 Updated by The Foreman Bot about 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 10 months ago

  • Target version changed from Team Daniel backlog to Team Marek Iteration 18

#9 Updated by Marek Hulán 10 months ago

  • Target version changed from Team Marek Iteration 18 to Team Marek Iteration 19

#10 Updated by Marek Hulán 9 months ago

  • Target version changed from Team Marek Iteration 19 to Team Marek Iteration 20

#11 Updated by Marek Hulán 8 months ago

  • Target version changed from Team Marek Iteration 20 to Foreman - Team Marek Iteration 21

#12 Updated by Marek Hulán 7 months ago

  • Target version changed from Foreman - Team Marek Iteration 21 to Foreman - Team Marek Iteration 22

#13 Updated by Marek Hulán 7 months ago

  • Target version changed from Foreman - Team Marek Iteration 22 to Foreman - Team Marek Iteration 23

#14 Updated by Marek Hulán 6 months ago

  • Target version changed from Foreman - Team Marek Iteration 23 to Foreman - Team Marek Iteration 24

#15 Updated by Marek Hulán 5 months ago

  • Target version changed from Foreman - Team Marek Iteration 24 to Team Marek Iteration 25

Also available in: Atom PDF