# ansible\_user\_id has incorrect value when overriding playbook sudo value in a task

**URL:** <https://forum.ansible.com/t/ansible-user-id-has-incorrect-value-when-overriding-playbook-sudo-value-in-a-task/14876>\
**Category:** Ansible Project\
**Created:** [March 27, 2014, 9:55pm UTC](https://forum.ansible.com/t/ansible-user-id-has-incorrect-value-when-overriding-playbook-sudo-value-in-a-task/14876 "2014-03-27T21:55:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ramon](https://avatars.discourse-cdn.com/v4/letter/r/34f0e0/32.png) [@ramon](https://forum.ansible.com/u/ramon)\
**Post date:** [March 27, 2014, 9:55pm UTC](https://forum.ansible.com/t/ansible-user-id-has-incorrect-value-when-overriding-playbook-sudo-value-in-a-task/14876/1 "2014-03-27T21:55:52Z")

</div>

Hi All,

Perhaps I don’t understand the ansible\_user\_id variable, but consider the following cases:

[https://gist.github.com/ramondelafuente/9819526](https://gist.github.com/ramondelafuente/9819526)

When you set a single task to sudo:no when the playbook has sudo: yes (or the other way around), ansibile\_ssh\_user has an unexpected value.  
The task runs with the proper user.

Is there currently a reliable way to get the actual user that runs a task in a variable?

Kind regards,

Ramon de la Fuente  
@F\_U\_E\_N\_T\_E
