Description of problem: Installation on GCE with cloudprovider enabled failed at TASK [openshift_cloud_provider : Configure GCE cloud provider] In https://github.com/openshift/openshift-ansible/blob/master/inventory/hosts.example#L293 no such option required. Version-Release number of the following components: openshift-ansible-3.9.0-0.24.0.git.0.735690f.el7.noarch.rpm ansible-2.4.2.0-2.el7.noarch # ansible --version ansible 2.4.2.0 config file = /etc/ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.13 (default, Jan 12 2017, 17:59:37) [GCC 6.3.1 20161221 (Red Hat 6.3.1-1)] How reproducible: Always Steps to Reproduce: 1. Install OCP with openshift-ansible $ ansible-playbook -i hosts openshift-ansible/playbooks/deploy_cluster.yml Actual results: TASK [openshift_cloud_provider : Configure GCE cloud provider] ***************** Thursday 25 January 2018 10:20:01 +0000 (0:00:00.317) 0:06:10.899 ****** fatal: [qe-wmeng.rhcloud.com]: FAILED! => {"msg": "'openshift_gcp_project' is undefined"} NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @/home/slave4/workspace/Launch Environment Flexy/private-openshift-ansible/playbooks/deploy_cluster.retry Expected results: Installation succeeds Additional info:
Clayton added some variables to openshift_cloud_provider that only have their defaults defined in roles/openshift_gcp/defaults/main.yml can openshift_cloud_provider just import defaults from that role or do we need to copy the actual file or refactor this in some other manner? See https://github.com/openshift/openshift-ansible/commit/949f4eacd2aa47833e1283de284aaed1c7ce91fe
Proposed fix: https://github.com/openshift/openshift-ansible/pull/6976
Fixed. openshift-ansible-3.9.0-0.45.0.git.0.05f6826.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. https://access.redhat.com/errata/RHBA-2018:0489