Description of problem: Installation failed when building env behind proxy on openstack Version-Release number of the following components: openshift-ansible-3.6.153-1.git.0.5a6bf7d.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1.Set the following options in ansible inventory to build env using proxy openshift_http_proxy=http://proxy.x.com:x openshift_https_proxy=http://proxy.x.com:x openshift_no_proxy="169.254.169.254" 2.Start installer Actual results: TASK [openshift_facts : Gather Cluster facts and set is_containerized if needed] *** Tuesday 18 July 2017 08:55:48 +0000 (0:00:00.086) 0:00:28.929 ********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'no_proxy_internal_hostnames' fatal: [openshift-x.com]: FAILED! => { "changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_7JbNKe/ansible_module_openshift_facts.py\", line 2601, in <module>\n main()\n File \"/tmp/ansible_7JbNKe/ansible_module_openshift_facts.py\", line 2588, in main\n protected_facts_to_overwrite)\n File \"/tmp/ansible_7JbNKe/ansible_module_openshift_facts.py\", line 1992, in __init__\n protected_facts_to_overwrite)\n File \"/tmp/ansible_7JbNKe/ansible_module_openshift_facts.py\", line 2058, in generate_facts\n facts = set_proxy_facts(facts)\n File \"/tmp/ansible_7JbNKe/ansible_module_openshift_facts.py\", line 1673, in set_proxy_facts\n auto_hosts = common['no_proxy_internal_hostnames'].split(',')\nKeyError: 'no_proxy_internal_hostnames'\n", "module_stdout": "" } MSG: MODULE FAILURE to retry, use: --limit @/home/slave5/workspace/Launch-Environment-Flexy/private-openshift-ansible/playbooks/byo/config.retry Expected results: Additional info:
This bug blocks testing on ocp-3.6 cluster with proxy used
https://github.com/openshift/openshift-ansible/pull/4794
Verify this bug with openshift-ansible-3.6.167-1.git.0.0ce5583.el7.noarch.rpm ocp-3.6 installation with global proxy configured was successful.
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