Bug 1637079 - Docker registry sync does not use HTTP proxy configuration.
Summary: Docker registry sync does not use HTTP proxy configuration.
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.3.3
Hardware: x86_64
OS: Linux
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Mirek Długosz
Depends On:
TreeView+ depends on / blocked
Reported: 2018-10-08 14:51 UTC by Jan Gerrit Kootstra
Modified: 2022-04-06 18:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-12-03 12:53:35 UTC
Target Upstream Version:

Attachments (Terms of Use)
registry created (41.31 KB, image/png)
2018-10-09 20:34 UTC, jcallaha
no flags Details

Description Jan Gerrit Kootstra 2018-10-08 14:51:14 UTC
Description of problem:

Adding a new Docker registry on a Satellite 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.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure Satellite 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

Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=1333595 solution does not seem to work for https://access.redhat.com/support/cases/#/case/02180843

Comment 1 jcallaha 2018-10-09 20:34:20 UTC
Created attachment 1492186 [details]
registry created

Creating the named registry works for me.

Comment 2 Jan Gerrit Kootstra 2018-10-09 20:51:14 UTC
In my case one day it seems to work, a few days later a resubmit fails.

Comment 6 Bryan Kearney 2019-11-04 14:34:03 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 7 Bryan Kearney 2019-12-03 12:53:35 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 8 agilmore2 2022-04-06 18:43:19 UTC
Pretty sure that https://bugzilla.redhat.com/show_bug.cgi?id=1893617 fixes this.

Note You need to log in before you can comment on or make changes to this bug.