Description of problem: When set "openshift_generate_no_proxy_hosts=False" in inventory hosts file, openshift masters, nodes, and etcd hosts would be still included in "NO_PROXY". Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.86-1.git.0.e221ac1.el7.noarch How reproducible: Always Steps to Reproduce: 1. Set "openshift_generate_no_proxy_hosts=False" in inventory hosts file 2. Set "openshift_no_proxy='test.local'" in inventory hosts file 2. Run "ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml" Actual results: Check the variable of NO_PROXY in master,docker configuration. <--snip--> NO_PROXY='.cluster.local,host-x-172-76.redhat.com,host-x-172-89.redhat.com,test.local' Expected results: Don't add those hostnames to the openshift_no_proxy list when set "openshift_generate_no_proxy_hosts=False" Additional info:
Proposed fix https://github.com/openshift/openshift-ansible/pull/1828
Verified with openshift-ansible-3.0.90-1.git.0.a077b68.el7.noarch * openshift_generate_no_proxy_hosts=False, openshift_no_proxy='test.local' test.local and the host itself were set in NO_PROXY * openshift_generate_no_proxy_hosts=False, don't set openshift_no_proxy the host itself were set in NO_PROXY I agree with this kind of set as it's safer. So move it to verified.
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/RHBA-2016:1208