hi,
I’v got a weird problem with copy module.
sudo ansible-playbook ./test.yml -e host=vmldmz
PLAY [vmldmz-haproxy4] ********************************************************
GATHERING FACTS ***************************************************************
ok: [vmldmz]
TASK: [copy preferences] ******************************************************
failed: [vmldmz] => {“failed”: true}
msg: unsupported parameter for module: original_basename
FATAL: all hosts have already failed – aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/var/tmp/ansible/test.retry
vmldmz : ok=1 changed=0 unreachable=0 failed=1
here is my simple playbook:
check to see if you have installed ansible 1.2 over <=1.1, modules were moved and you seem to be picking up a mix of new and old ones.
thanks for you answer
but I’v purged share/ansible/ and
/usr/local/lib/python2.6/dist-packages/ansible
reinstalled python27 from scratch and use virtualenv
another thing to do ?
thanks again
try using from github checkout and sourcing ansilbe/hacking/env-setup, that will force everything to use the checkout. if problem goes away you might still have a lingering old install somewhere else that python is looking at.
I found an old copy modules in the directory tree under the playbook
I don’t know why but I was used rather other PATHs even using virtual env or copying the whole tree on another machine
thanks
Yep, clean that up and you’ll be fine.
Ansible is configured to look for modules in subdirectories (categorized ones) first, so this may have happened if you somehow had a library path that didn’t include the newly categorized install ones, like if you had done a previous make install or something?
Anyway, on a clean machine you should be good to go.
I just had this same problem. For me, it turned out that my umask was too tight (0077) when I did the install and I couldn’t read /usr/share/ansible. I deleted it and re-installed it a few times before I figured out my mistake. D’oh!