Description of problem: Since the upgrade to ansible-2.0.1.0-2.fc23.noarch my playbooks are behaving randomly. For example the copy actions for my bash environment for my own user and root. First it fails for root. Second try, nothing changed, it succeeds. More tasks behave like this which can be considered a critical drop in quality and reliability of Ansible. TASK [common : copy bash environment for keesj] ******************************** ok: [127.0.0.1] => (item={u'dest': u'.bash_profile', u'src': u'bash_profile'}) ok: [127.0.0.1] => (item={u'dest': u'.bashrc', u'src': u'bashrc'}) ok: [127.0.0.1] => (item={u'dest': u'.bash_aliases', u'src': u'bash_aliases'}) ok: [127.0.0.1] => (item={u'dest': u'.forward', u'src': u'forward'}) TASK [common : copy bash environment for root] ********************************* fatal: [127.0.0.1]: FAILED! => {"failed": true, "msg": "failed to resolve remote temporary directory from ansible-tmp-1461052804.64-126912064857518: `( umask 22 && mkdir -p \"` echo $HOME/.ansible/tmp/ansible-tmp-1461052804.64-126912064857518 `\" && echo \"` echo $HOME/.ansible/tmp/ansible-tmp-1461052804.64-126912064857518 `\" )` returned empty string"} NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @workstation.retry PLAY RECAP ********************************************************************* 127.0.0.1 : ok=18 changed=0 unreachable=0 failed=1 [root@defiant Ansible]# ansible-playbook -i workstation_hosts workstation.yml --ask-vault-pass -t copy_bash_keesj,copy_bash_root Vault password: PLAY *************************************************************************** TASK [setup] ******************************************************************* ok: [127.0.0.1] TASK [common : copy bash environment for keesj] ******************************** ok: [127.0.0.1] => (item={u'dest': u'.bash_profile', u'src': u'bash_profile'}) ok: [127.0.0.1] => (item={u'dest': u'.bashrc', u'src': u'bashrc'}) ok: [127.0.0.1] => (item={u'dest': u'.bash_aliases', u'src': u'bash_aliases'}) ok: [127.0.0.1] => (item={u'dest': u'.forward', u'src': u'forward'}) TASK [common : copy bash environment for root] ********************************* ok: [127.0.0.1] => (item={u'dest': u'.bash_profile', u'src': u'bash_profile_root'}) ok: [127.0.0.1] => (item={u'dest': u'.bashrc', u'src': u'bashrc_root'}) ok: [127.0.0.1] => (item={u'dest': u'.bash_aliases', u'src': u'bash_aliases_root'}) ok: [127.0.0.1] => (item={u'dest': u'.forward', u'src': u'forward'}) PLAY *************************************************************************** TASK [setup] ******************************************************************* ok: [127.0.0.1] PLAY RECAP ********************************************************************* 127.0.0.1 : ok=4 changed=0 unreachable=0 failed=0 Version-Release number of selected component (if applicable): ansible-2.0.1.0-2.fc23.noarch How reproducible: Add this as a task. - name: copy bash environment for keesj copy: src={{ item.src }} dest=/home/keesj/{{ item.dest }} owner=keesj group=keesj mode=644 with_items: - { src: "bash_profile", dest: ".bash_profile" } - { src: "bashrc", dest: ".bashrc" } - { src: "bash_aliases", dest: ".bash_aliases" } - { src: "forward", dest: ".forward" } tags: copy_bash_keesj - name: copy bash environment for root copy: src={{ item.src }} dest=/root/{{ item.dest }} owner=root group=root mode=644 with_items: - { src: "bash_profile_root", dest: ".bash_profile" } - { src: "bashrc_root", dest: ".bashrc" } - { src: "bash_aliases_root", dest: ".bash_aliases" } - { src: "forward", dest: ".forward" } tags: copy_bash_root Then run it, sometimes it works, sometimes it doesn't. But I'm not sure it's because of this task, set of files and configurations specific. It's more about this warning that pop-ups randomly in this task and others: fatal: [127.0.0.1]: FAILED! => {"failed": true, "msg": "failed to resolve remote temporary directory from ansible-tmp-1461052804.64-126912064857518: `( umask 22 && mkdir -p \"` echo $HOME/.ansible/tmp/ansible-tmp-1461052804.64-126912064857518 `\" && echo \"` echo $HOME/.ansible/tmp/ansible-tmp-1461052804.64-126912064857518 `\" )` returned empty string"} Expected results: A major version update of course can have syntax problems with old configurations. But these results are so random it can't be syntax but rather the quality of Ansible. Additional info: I will downgrade, I don't think Ansible 2.0 is ready yet for Fedora.
This is this upstream bug: https://github.com/ansible/ansible/issues/13876 Note that it's very sporadic. Some folks see it often, many others don't see it at all. There's a partial fix that should be out in 2.0.2.0 which should be out soon. You can remove the 'ansible' package and install 'ansible1.9' if you wish to stay on the 1.9.x releases for now.
ansible-2.0.2.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-679c4ddd3c
ansible-2.0.2.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd3cf8e7d0
ansible-2.0.2.0-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ab154c56dd
ansible-2.0.2.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-56e02a47c7
ansible-2.0.2.0-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-09ad0ba4a5
ansible-2.0.2.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-679c4ddd3c
ansible-2.0.2.0-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd3cf8e7d0
ansible-2.0.2.0-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ab154c56dd
Confirmed, ansible-2.0.2.0-1.fc23 does work as expected, thanks!
ansible-2.0.2.0-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-09ad0ba4a5
ansible-2.0.2.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-56e02a47c7
ansible-2.0.2.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
ansible-2.0.2.0-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
ansible-2.0.2.0-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
ansible-2.0.2.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
ansible-2.0.2.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.