# Ansible running Galera arbitrator "run" command as root although "become: yes" is not used

**URL:** <https://forum.ansible.com/t/ansible-running-galera-arbitrator-run-command-as-root-although-become-yes-is-not-used/26586>\
**Category:** Ansible Developer\
**Created:** [January 29, 2018, 3:04pm UTC](https://forum.ansible.com/t/ansible-running-galera-arbitrator-run-command-as-root-although-become-yes-is-not-used/26586 "2018-01-29T15:04:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hicham\_Seffendji](https://avatars.discourse-cdn.com/v4/letter/h/22d042/32.png) [@Hicham\_Seffendji](https://forum.ansible.com/u/Hicham_Seffendji)\
**Post date:** [January 29, 2018, 3:04pm UTC](https://forum.ansible.com/t/ansible-running-galera-arbitrator-run-command-as-root-although-become-yes-is-not-used/26586/1 "2018-01-29T15:04:37Z")

</div>

Hi,

I have the following **arbitrator\_run** role in Ansible :

- name: Run garb  
service:  
name: garb  
state: started

The role in question is called from the main playbook as follows:

- name: Run arbitrator  
hosts: galera\_arbitrator  
roles:
- { role: arbitrator\_run}

As you can see, I am not using “become: yes” and yet Ansible tries to execute “service garb start” with escalated privileges.

How do I know it’s trying to run it with escalated privileges? It throws the same error when I run it manually after a “sudo su -”. The same command succeeds though when I manually run it without “sudo su -”.

However, there are some “become: yes” arguments in previous instructions (before “Run arbitrator”) but my understanding is each “become: yes” will be local to the bloc where it belongs.

Any assistance would be appreciated.

Thanks,  
Hicham

---

<div class="post-metadata">

**Author:** ![Karol\_Czeryna](https://avatars.discourse-cdn.com/v4/letter/k/ed655f/32.png) [@Karol\_Czeryna](https://forum.ansible.com/u/Karol_Czeryna)\
**Post date:** [January 29, 2018, 3:48pm UTC](https://forum.ansible.com/t/ansible-running-galera-arbitrator-run-command-as-root-although-become-yes-is-not-used/26586/2 "2018-01-29T15:48:47Z")

</div>

Hi Hicham!

You can try to run your playbook with \*-vvvv\* to see verbose messages, or you can export ANSIBLE\_DEBUG=1 to see what is going on underneath.  
But… first of all - I would recommend to you to check your ansible.cfg ([http://docs.ansible.com/ansible/latest/intro\_configuration.html#become](http://docs.ansible.com/ansible/latest/intro_configuration.html#become))

Best,  
Karol