# Bizarre behavior.

**URL:** <https://forum.ansible.com/t/bizarre-behavior/13655>\
**Category:** Ansible Project\
**Created:** [October 10, 2013, 1:51pm UTC](https://forum.ansible.com/t/bizarre-behavior/13655 "2013-10-10T13:51:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Barronville](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@Jonathan\_Barronville](https://forum.ansible.com/u/Jonathan_Barronville)\
**Post date:** [October 10, 2013, 1:51pm UTC](https://forum.ansible.com/t/bizarre-behavior/13655/1 "2013-10-10T13:51:13Z")

</div>

Hello everyone!

I have a very simple Vagrant + Ansible setup here: [https://github.com/jonathanmarvens/taylor-otwell-vagrant-setup/tree/55945af0e80e6e4208e209b9dfb71a0efbb7bfc5/ansible](https://github.com/jonathanmarvens/taylor-otwell-vagrant-setup/tree/55945af0e80e6e4208e209b9dfb71a0efbb7bfc5/ansible) .

On vagrant up, I provision using a direct shell command via Vagrant’s shell provisioner. However, Ansible (not Vagrant) has been behaving somewhat bizarrely lately ☹ . If Ansible is ran in the state of the commit above, it fails with the error “msg: Failed to find required executable npm” which isn’t true because NPM is installed at the beginning, but once it fails, NPM, for some odd reason, is no longer installed o.0 . I tested this by commenting out the the NPM package installations … everything succeeds and at completion, NPM is still on the system. I’ve also tried this on a non-Vagrant machine and I get the same results, so I know the issue is not being produced by Vagrant.

I have absolutely no idea what is going on, so any help would be greatly appreciated.

Thanks in advance.  
Have a good one!

- Jonathan

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [October 11, 2013, 12:10am UTC](https://forum.ansible.com/t/bizarre-behavior/13655/2 "2013-10-11T00:10:10Z")

</div>

I’d have to see the whole playbook to verify but I’m a little suspicous that we’re deleting npm 🙂

---

<div class="post-metadata">

**Author:** ![Jonathan\_Barronville](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@Jonathan\_Barronville](https://forum.ansible.com/u/Jonathan_Barronville)\
**Post date:** [October 11, 2013, 10:05am UTC](https://forum.ansible.com/t/bizarre-behavior/13655/3 "2013-10-11T10:05:45Z")

</div>

Hi Michael!

Thanks for the response.

The playbook is here: [https://github.com/jonathanmarvens/taylor-otwell-vagrant-setup/blob/55945af0e80e6e4208e209b9dfb71a0efbb7bfc5/ansible/main.yml](https://github.com/jonathanmarvens/taylor-otwell-vagrant-setup/blob/55945af0e80e6e4208e209b9dfb71a0efbb7bfc5/ansible/main.yml) .

Thanks again.  
Be well!

- Jonathan

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [October 11, 2013, 12:53pm UTC](https://forum.ansible.com/t/bizarre-behavior/13655/4 "2013-10-11T12:53:55Z")

</div>

Looks like you are doing some safe-upgrades in a handler, maybe that has something to do with it.