I've got ask_sudo_pass = True
on ~/.ansible.cfg Both are run as the user 'ansible'. So I'm guessing I can rule that out? On Wednesday, 5 March 2014 15:26:44 UTC, Michael DeHaan wrote: > > The ansible command is probably running as your username vs "ansible", do > you need to request sudo: true ? > > -- Michael > > On Mar 5, 2014, at 10:24 AM, Makimoto Marakatti > <[email protected]<javascript:>> > wrote: > > Hi > > I'm having an issue I can't even begin to understand: I'm trying to > replace some files and I can do that without any issue if I do that from an > ad-hoc command. But if I try to do the SAME command from a playbook, it > fails. > > This is ansible 1.5 on centos 6.4 on the master and centos 6.x on the > managed boxes > > Here the successful run ad-hoc: > > $ ansible antpitta0 -m copy -a > "src=/deployment/files/profiled/tod_0dm/etc/bashrc > dest=/etc/bashrc owner=root group=root mode=0644 force=yes" > sudo password: > previous known host file not found > previous known host file not found > previous known host file not found > antpitta0 | success >> { > "changed": true, > "dest": "/etc/bashrc", > "gid": 0, > "group": "root", > "md5sum": "eb04806e1f907b98b3afa619b9a8cf64", > "mode": "0644", > "owner": "root", > "size": 2025, > "src": "/tmp/ansible-tmp-1394031344.37-53546288343003/source", > "state": "file", > "uid": 0 > } > > > > And here the failing playbook run: > > $ ansible-playbook tod-0dm-new.yml > sudo password: > > PLAY [tod-0dm] > **************************************************************** > > TASK: [copy bashrc to the server] > ********************************************* > previous known host file not found > previous known host file not found > ok: [antpitta0] > > TASK: [copy profile to the server] > ******************************************** > previous known host file not found > previous known host file not found > previous known host file not found > failed: [antpitta0] => {"failed": true, "md5sum": > "4c781f5c55a1a62ac9ad09574abc9ae6"} > msg: Destination /etc not writable > > FATAL: all hosts have already failed -- aborting > > PLAY RECAP > ******************************************************************** > to retry, use: --limit @/deployment/home/tod-0dm-new.retry > > antpitta0 : ok=1 changed=0 unreachable=0 failed= > 1 > > > > And here the contents of my playbook: > > $ cat tod-0dm-new.yml > --- > #- hosts: 0dm-tod > - hosts: antpitta0 > name : tod-0dm > gather_facts: False > user: ansible > tasks: > - name: copy bashrc to the server > copy: src=/deployment/files/profiled/tod_0dm/etc/bashrc > dest=/etc/bashrc > owner=root group=root mode=0644 force=yes > > > So what am I doing wrong here??? > > -- > 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] <javascript:>. > To post to this group, send email to [email protected]<javascript:> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/e24c61f1-d0e5-416a-b69b-283d9963141e%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/e24c61f1-d0e5-416a-b69b-283d9963141e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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/d85f6cb5-aa76-4e57-8c45-b7d6bdc672dc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
