Perhaps you should provide the details of the playbook as well here. There are many possibilities. For example, this can happen due to the ssh user in the cron. When you run the playbook in a ssh session, you are running with you as the logged-in user. The cron user must have similar privileges on the remote host (if you are using passwordless ssh setup, for instance) for it to succeed.
Regards -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/11256d35-7d3e-4c63-a7fa-e4b9cf00ad77%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
