Red Hat Bugzilla – Bug 1495142
All the internal hosts should be added to NO_PROXY
Last modified: 2017-11-28 17:12:28 EST
Description of problem: Only the host itself added to NO_PROXY in /etc/sysconfig/atomic-openshift-master-api, /etc/sysconfig/atomic-openshift-master-controllers, /etc/sysconfig/atomic-openshift-node and /etc/origin/master/master-config.yaml. That result in `oc logs..` failed. We should add all the internal hosts to NO_PROXY at least. Version-Release number of the following components: openshift-ansible-3.7.0-0.126.4.git.0.3fc2b9b.el7.noarch.rpm How reproducible: always Steps to Reproduce: 1.Trigger proxy installation <--snip--> openshift_https_proxy=http://xxxx.redhat.com:3128 openshift_http_proxy=http://xxxx.redhat.com:3128 <--snip--> Actual results: Installation succeed, but only the host itself added to NO_PROXY. Expected results: All the internal hosts added to NO_PROXY. Additional info:
I believe I have reproduced this error in a 1m2n cluster. The problem is even worse in that scenario as the nodes will fail to register completely. Just as you described in the OP, the only host entry in the sysconfig proxy settings was for the host I was looking at, along with the boilerplate '.svc...' items. Trying this now on OCP 3.6
I have ran tests and verified this bug for OCP 3.7 when proxy parameters are set. I am working on identifying the source of the regression now.
Tim, I submitted a PR for the issue, at least it worked for me. But uncertain if that's a good way to fix. Hopefully could help you to identify the issue.
Might be a fix: https://github.com/openshift/openshift-ansible/pull/5569/files
Ouch. Since that PR has lingered for almost a month it has gotten out of sync. I'll try fixing it up and running the 3.7 proxy tests again.
I've fixed up the rebase problem with the original patch you provided and I have successfully tested the patch. Results are shown in github: https://github.com/openshift/openshift-ansible/pull/5569#issuecomment-338001818
Verified in openshift-ansible-3.7.0-0.178.0.git.0.27a1039.el7.noarch.rpm Proxy variables added correctly. Thanks Tim.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188