As noted in the issue above, previously this has been caused by setting the
ansible_ssh_user variable in inventory. I have tested the provided playbook
with both the 1.6.2 and devel branches and cannot reproduce the issue
outside of setting that variable in inventory.

Holding the issue open for now, but most likely the inventory variable is
the issue here.


On Thu, Jun 5, 2014 at 8:16 AM, Alex Dupuy <[email protected]> wrote:

> On Wednesday, April 2, 2014 10:04:30 PM UTC+2, Michael DeHaan wrote:
>>
>> Sounds like you are saying the remote_user on the task attribute is not
>> overriding the remote_user on the host.
>>
>> If you see this behavior on 1.5.3 and later, can you please check to see
>> if you see this behavior on the development branch, and if so, file a bug?
>>
>>
> I am seeing this issue with 1.5.5 and now 1.6.2, so I have filed a bug:
> https://github.com/ansible/ansible/issues/7673
>
> @alex
>
>  --
> 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/6c2d8d75-4076-4acb-86c0-a994cf2e569e%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/6c2d8d75-4076-4acb-86c0-a994cf2e569e%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 [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/CAMFyvFjDgaCQ8o8LnmtXXfUXcQMVxd1n3yQnav63CPpKk-gHHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to