Gilles, thanks for the reply.
I have double checked that the `git` task is indeed executed by the
intended remote user, vagrant, not root. Sudo is off in both Vagrant and
Ansible configuration.
I have a new discovery to the problem though. The reported issue happened
with Ubuntu 14.04 ("phusion/ubuntu-14.04-amd64" vagrant image) being the
target box. Using the exact same Vagrant configuration and Ansible
playbook, I tried Ubuntu 12.04 ("hashicorp/precise64" vagrant image) and,
surprisingly, the `git` task was successfully executed. How odd.
My very first thought of the different result was that, perhaps,
`AllowAgentForwarding` was disabled in `sshd_config` in this particular
Ubuntu 14.04 image. I checked it but that wasn't the case.
Now, I am left with a big question mark on what's causing the issue for the
Ubuntu 14.04 box. It could be something to do with the particular image
that I use, or something to do with Ubuntu 14.04 in general. I don't know
what else I can do to diagnose the issue. Any thoughts?
On Thursday, May 8, 2014 3:21:32 PM UTC-7, Gilles Cornu wrote:
>
>
>
>
>> Your play snippet and execution log excerpt do not allow to know if the
>> `git` task is executed by the remote user (in this example `vagrant`) and I
>> suspect that this task is in fact executed by root, due to some `sudo: yes`
>> (enabled either in Vagrant settings or in your playbook file).
>>
>
> Oops sorry, just a little correction on what I wrote before: Your play is
> complete and does not include any `sudo: yes`, so I suppose that you are
> using the `ansible.sudo = true` option in the vagrant provisioner settings.
> Could confirm?
>
--
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/48477cac-85ab-44e1-80ee-8d6d6d7b42e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
