-u is remote_user which does not map to local actions which are normally executed as the user which executed ansible, since local action does not 'log in' the only other was to change the user would be using privilege escalation (sudo/su/etc).
On Wed, May 13, 2015 at 1:26 PM, John Oliver <[email protected]> wrote: > I did sort of get around this by passing 'sudo: no' to that one task. > > -- > 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/da12e952-0556-4825-8c8c-cc530956c70d%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Brian Coca -- 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/CAJ5XC8ndSj0vhXXNpK7ewU0HgfK%2B3rRb%2Br-oAN88HaW0igSU3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
