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): 6.3.3 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
Created attachment 1492186 [details] registry created Creating the named registry works for me.
In my case one day it seems to work, a few days later a resubmit fails.
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.
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.
Pretty sure that https://bugzilla.redhat.com/show_bug.cgi?id=1893617 fixes this.