Description of problem: When installing Openshift on Openstack using multi-master setup I have the following error: TASK [kuryr : Ensure project exists] ******************************************* fatal: [master-1.openshift.example.com]: FAILED! => {"changed": false, "msg": {"cmd": "/bin/oc adm new-project kuryr --admin-role=admin --node-selector=", "results": {}, "returncode": 1, "stderr": "error: project kuryr already exists\n", "stdout": ""}} fatal: [master-2.openshift.example.com]: FAILED! => {"changed": false, "msg": {"cmd": "/bin/oc adm new-project kuryr --admin-role=admin --node-selector=", "results": {}, "returncode": 1, "stderr": "error: project kuryr already exists\n", "stdout": ""}} changed: [master-0.openshift.example.com] The step of ensuring the existence of the kuryr openshift project fails. Version-Release number of the following components: OSP14 openshift-ansible-3.11.95-1.git.0.d080cce.el7.noarch ansible-2.6.14-1.el7ae.noarch ansible 2.6.14 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/cloud-user/.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.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag
This is caused by a race condition, where multiple masters will try and create the project if it doesn't yet exist. Note that this means that re-running the playbook should allow you to progress. A more permanent fix is here: https://github.com/openshift/openshift-ansible/pull/11351
Verified with: 3.11.97
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-2019:1605