Bug 1544682

Summary: HTTP and HTTPS Proxy set on docker-registry during installation
Product: OpenShift Container Platform Reporter: Kim Borup <kborup>
Component: Image RegistryAssignee: Ben Parees <bparees>
Status: CLOSED DUPLICATE QA Contact: Dongbo Yan <dyan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: aos-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-13 14:55:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kim Borup 2018-02-13 09:45:01 UTC
Description of problem:

When deploying openshift 3.7, and using http/https proxy for installing. The default-registry gets HTTP and HTTPS Proxy added, when the proxy is added without the correct NO_PROXY it is unable to talk to the kubernetes backend via ip or name. 

This itself causes a problem cause you will be unable to push to the internal registry right after an installation. 

After removing the variables from the docker-registry dc, it is possible to push to the registry again as it is able to talk to kubernetes. 

I dont find any reason for setting HTTP and HTTPS proxy for the docker-registry itself.


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

How reproducible:
Every install where proxy are involved. 

Steps to Reproduce:
1. Setup proxy in Ansible playbook 
2. Install Openshift
3. Try to push image to registry
4. Inspect pod after push failure, where it will show http , https , no_proxy settings which will make the failure. 


Actual results:
Unable to push images into the registry

Expected results:
Being able to push images into the registry. 

Additional info:

Comment 1 Ben Parees 2018-02-13 14:55:47 UTC

*** This bug has been marked as a duplicate of bug 1511870 ***