Red Hat Bugzilla – Bug 1470165
NO_PROXY was missed in /etc/sysconfig/docker
Last modified: 2017-08-16 15:51 EDT
Description of problem:
Trigger containerized installation with http_proxy/https_proxy settings, it resulted in that there was no no_proxy variable set in /etc/sysconfig/docker.
Version-Release number of the following components:
Steps to Reproduce:
1. Trigger containerized installation with http_proxy/https_proxy settings
NO_PROXY missed in /etc/sysconfig/docker
# grep "PROXY" /etc/sysconfig/docker
NO_PROXY set correctly in /etc/sysconfig/docker
Can you verify the permutations we have here in this gist are correct? We tried to match the upstream documentation as best we could with what we think the expected results should be from using them:
Per docs in: https://docs.openshift.org/latest/install_config/install/advanced_install.html#advanced-install-configuring-global-proxy
(In reply to Tim Bielawa from comment #4)
(Seems the Raw format is more readable :) )
If nothing proxy variables specified, is there a reason to set `NO_PROXY`? (Anyway I don't object to this setting as I don't think it would get something hurt)
The rest looks good to me if they're for Docker configurations.
For masters/nodes/builddefaults proxy settings, we should add `openshift_master_portal_net` and `osm_cluster_network_cidr` as defaults in NO_PROXY. (We don't add it to Docker configurations as Docker doesn't support CIDRs)
Working on this again in https://github.com/openshift/openshift-ansible/pull/4762
Verified with openshift-ansible-3.6.170-1.git.0.aef02f6.el7.noarch.rpm
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.