# Issue with become\_user

**URL:** <https://forum.ansible.com/t/issue-with-become-user/24359>\
**Category:** Ansible Project\
**Created:** [April 29, 2017, 11:41pm UTC](https://forum.ansible.com/t/issue-with-become-user/24359 "2017-04-29T23:41:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Oakes](https://avatars.discourse-cdn.com/v4/letter/r/e56c9b/32.png) [@Ryan\_Oakes](https://forum.ansible.com/u/Ryan_Oakes)\
**Post date:** [April 29, 2017, 11:41pm UTC](https://forum.ansible.com/t/issue-with-become-user/24359/1 "2017-04-29T23:41:41Z")

</div>

Hey all. I’m attempting to write a small playbook that installs oh-my-zsh on a remote host. The final step of the playbook is to run the ohmyzsh install tool script.

- name: Apply zsh sript  
shell: sh -c “$(curl -fsSL [https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh](https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh))”  
become\_user: ec2-user

The problem is that is installing the configurations at /root/.oh-my-zsh instead of the desirable _/home/ec2-user/.oh-my-zsh._ Am I doing something wrong here?

If I log into the remote instance and run that shell command manually, all is well - the configurations end up in _/home/ec2-user/.oh-my-zsh_.

However, when I attempt to do it through Ansible and this task, the configurations end up in _/root/.oh-my-zsh_ instead of _/home/ec2-user/.oh-my-zsh._

Any thoughts on what I’m doing wrong? In my hosts file, my “ansible\_user” is set to “ec2-user” , so that’s the only thing I could think of that could be causing an issue.  
If anyone can point me in the right direction I’d appreciate it!

Thanks.

-Ryan

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [May 1, 2017, 6:28pm UTC](https://forum.ansible.com/t/issue-with-become-user/24359/2 "2017-05-01T18:28:08Z")

</div>

become\_user does not imply `become: true`

You will also need to instruct ansible to actually use become.
