Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1771942

Summary:	[PROXY]Deployer pod cannot ready global proxy setting like builder pod
Product:	OpenShift Container Platform	Reporter:	Wenjing Zheng <wzheng>
Component:	openshift-controller-manager	Assignee:	Tomáš Nožička <tnozicka>
Status:	CLOSED WONTFIX	QA Contact:	zhou ying <yinzhou>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	aos-bugs, maszulik, mfojtik, sttts, wewang
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	workloads
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-13 14:43:23 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 Wenjing Zheng 2019-11-13 09:59:41 UTC

Description of problem:
No proxy setting in deploy pod, so user cannot access external site inside deploy pod in a proxy enabled cluster:
[wzheng@openshift-qe 4.3ci]$ oc debug pods/nodejs-mongodb-example-1-deploy
Starting pod/nodejs-mongodb-example-1-deploy-debug ...
Pod IP: 10.128.2.55
If you don't see a command prompt, try pressing enter.
sh-4.2$ curl https://github.com
^C
sh-4.2$ env | grep PROXY
sh-4.2$ exit
exit

Build pod can:
[wzhengtest@openshift-qe 4.3ci]$ oc debug pods/django-psql-example-1-build
Starting pod/django-psql-example-1-build-debug, command was: openshift-sti-build --loglevel=0
Pod IP: 10.131.0.27
If you don't see a command prompt, try pressing enter.
sh-4.2# env | grep PROXY
NO_PROXY=xxxxxx
HTTPS_PROXY=http://xxxxxx
HTTP_PROXY=http://xxxxxx


Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-12-185229

How reproducible:
Always

Steps to Reproduce:
1.Set up a proxy enabled cluster
2.Trigger a deployment
3.Access github.com inside deployer pod
4.Try to get proxy setting inside deployer pod

Actual results:
Cannot get proxy setting inside deployer pod, so cannot access external site

Expected results:
Should can like builder pod.

Additional info:

Comment 1 Tomáš Nožička 2019-11-13 16:32:45 UTC

why should a deployer enable talking to external cluster when it should only talk back to the internal cluster API?

Comment 2 Wenjing Zheng 2019-11-14 01:42:39 UTC

Because we have scenario about deploy a git server pod and clone repo inside it: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-10678

It works in cluster which can access external site without proxy.

Comment 3 Tomáš Nožička 2019-11-14 12:18:24 UTC

If you deploy a git server that's fine but you don't control the logic inside the deploy pod, do you? That is just calling predefined oc command which uses inclusterconfig to talk back to apiserver and scale the RCs.

Please attach the DC yaml and deploy Pod yaml and the exact step how to reproduce your issue.

Comment 4 Wenjing Zheng 2019-11-18 10:42:11 UTC

Using git server is just an example, I just use a common deploy then try to access github with below steps:
In cluster-wide enabled proxy install cluster:
$ oc new-app ruby~https://github.com/openshift/ruby-ex
$ oc debug pods/ruby-ex-1-deploy
Starting pod/ruby-ex-1-deploy-debug ...
Pod IP: 10.131.0.79
If you don't see a command prompt, try pressing enter.
sh-4.2$ curl -v www.github.com
<no below output like same command in ruby-ex-1-build pod>

$ oc debug pods/ruby-ex-1-build
Starting pod/ruby-ex-1-build-debug, command was: openshift-sti-build --loglevel=0
Pod IP: 10.128.2.54
If you don't see a command prompt, try pressing enter.
sh-4.2# curl -v www.github.com
* About to connect() to www.github.com port 80 (#0)
*   Trying 192.30.253.113...
* Connected to www.github.com (192.30.253.113) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: www.github.com
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Content-length: 0
< Location: https://www.github.com/
< 
* Connection #0 to host www.github.com left intact

Comment 5 Tomáš Nožička 2019-11-18 12:11:06 UTC

I don't think deployer pod needs proxy, but hooks do.

Comment 6 Maciej Szulik 2020-02-13 14:43:23 UTC

I don't envision us doing this, closing as won't fix.