Closed mxmader closed 11 years ago
Yeah... seems that this is fixed by using the latest ansible 1.3 (master):
[root@ip-10-235-48-196 ansible-openshift_origin]# ansible-playbook --connection local site.yml
PLAY [all] ********************************************************************
GATHERING FACTS ***************************************************************
ok: [10.235.48.196]
TASK: [Setup OpenShift Origin Nightly Repo] ***********************************
changed: [10.235.48.196]
TASK: [Setup OpenShift Origin Nightly Supplemental Repo] **********************
changed: [10.235.48.196]
TASK: [Setup OpenShift Origin Stable] *****************************************
skipping: [10.235.48.196]
TASK: [Setup OpenShift Origin Nightly Supplemental Repo] **********************
skipping: [10.235.48.196]
TASK: [SELinux Enforcing (Targeted)] ******************************************
ok: [10.235.48.196]
TASK: [Ensure Installed - policycoreutils] ************************************
ok: [10.235.48.196]
TASK: [Ensure Installed - policycoreutils-python] *****************************
ok: [10.235.48.196]
TASK: [Ensure Install - firewalld] ********************************************
To get around this, I ran:
yum remove -y ansible
git clone https://github.com/ansible/ansible
cd ansible
python setup.py install
Then I re-ran the playbook.
Awesome, thanks! (sorry for the delay, been busy :X)
Perhaps this related to the following upstream ansible bug:
https://github.com/ansible/ansible/issues/3460
I will try this again with the ansible development branch and see what happens