I've heard this claimed before.
Doesn't the vagrant provisioner do something weird like SSH in and then run
Ansible, so the issue is with vagrant not doing the forwarding, regardless
if your SSH config is so set?
Either way, be sure you are using "-c ssh". If you are on Enterprise
Linux, Paramiko won't forward things.
On Thu, May 8, 2014 at 7:21 PM, tamakisquare <windbot...@gmail.com> wrote:
> I should mention that the verbose output from Ansible for the `git` task
> is also exactly the same in both cases.
>
>
> On Thursday, May 8, 2014 4:12:42 PM UTC-7, tamakisquare wrote:
>>
>> 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 ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/0b11710d-ce31-4ce8-96df-ccb650593b71%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/0b11710d-ce31-4ce8-96df-ccb650593b71%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgwdNMHrNt6cRF4TkqvAQoTS3-Qi6KOpJgwYCfnmSAsC9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
