# Issues with become

**URL:** <https://forum.ansible.com/t/issues-with-become/25512>\
**Category:** AWX Project\
**Created:** [September 18, 2017, 5:26pm UTC](https://forum.ansible.com/t/issues-with-become/25512 "2017-09-18T17:26:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcsloe](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mcsloe](https://forum.ansible.com/u/mcsloe)\
**Post date:** [September 18, 2017, 5:26pm UTC](https://forum.ansible.com/t/issues-with-become/25512/1 "2017-09-18T17:26:29Z")

</div>

I am having permission issues on the remote hosts when running playbooks.

I have reproduced the issue with a simple playbook:

# test setup

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [September 18, 2017, 5:35pm UTC](https://forum.ansible.com/t/issues-with-become/25512/2 "2017-09-18T17:35:51Z")

</div>

If you need to sudo enabled during the playbook run then you’ll need to turn on privilege escalation for the credential that you are using, or turn it on in the job template screen.

---

<div class="post-metadata">

**Author:** ![mcsloe](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mcsloe](https://forum.ansible.com/u/mcsloe)\
**Post date:** [September 18, 2017, 5:49pm UTC](https://forum.ansible.com/t/issues-with-become/25512/3 "2017-09-18T17:49:14Z")

</div>

I have the following set for the credentials being used:

`

Privilege Escalation Method: sudo  
Privilege Escalation Username: esadmin  
Privilege Escalation Password: (encrypted)

`  
I have also tried setting ‘Enable Privilege Escalation’ in the template.

I still get the same results.

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [September 18, 2017, 5:57pm UTC](https://forum.ansible.com/t/issues-with-become/25512/4 "2017-09-18T17:57:33Z")

</div>

Turn privilege escalation on for the job template

---

<div class="post-metadata">

**Author:** ![mcsloe](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mcsloe](https://forum.ansible.com/u/mcsloe)\
**Post date:** [September 18, 2017, 6:06pm UTC](https://forum.ansible.com/t/issues-with-become/25512/5 "2017-09-18T18:06:55Z")

</div>

I have this checked:  
Under TEMPLATES / setupDETAILS  
Enable Privilege Escalation?

Or am I missing a setting elsewhere in the UI?

Thanks

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [September 18, 2017, 6:42pm UTC](https://forum.ansible.com/t/issues-with-become/25512/6 "2017-09-18T18:42:31Z")

</div>

I do see where you have privilege escalation enabled, sorry about that.

Our output is going to differ a little bit from Ansible, when I run a similar test the privilege escalation does work for me.