Description of problem: Currently we only set http_proxy and https_proxy for atomic, this is insufficient for the case that the user needs to set NO_PROXY in /etc/atomic.conf to pull the system container images from the internal registry which doesn't need the proxy. Version-Release number of selected component (if applicable): openshift-ansible master branch (last commit id is 593ef65) How reproducible: always Steps to Reproduce: 1. see above 2. 3. Actual results: NO_RPOXY not allowed to set in /etc/atomic.conf Expected results: Installer should set NO_PROXY in /etc/atomic.conf Additional info:
NO_PROXY is not supported in /etc/atomic.conf. I've opened up https://github.com/projectatomic/atomic/pull/999 to add it.
PR: https://github.com/openshift/openshift-ansible/pull/4173 (for when atomic:999 is merged)
The PR adds no_proxy to /etc/atomic.conf. However, I don't believe it will be in the current releases so I've added an environment override for the atomic command until atomic:999 is released.
Updated and merged https://github.com/openshift/openshift-ansible/pull/4173
Verified with openshift-ansible-3.6.98-1.git.0.e651d65.el7.noarch.rpm # grep -nir "no_proxy" /etc/atomic.conf 26:no_proxy: .cluster.local,openshift-133.xx.redhat.com,openshift-145.xx.redhat.com
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/RHEA-2017:1716