Bizarre behavior.

Archives Ansible Project
1

Hello everyone!

I have a very simple Vagrant + Ansible setup here: 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 :frowning: . 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
2

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

3

Hi Michael!

Thanks for the response.

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

Thanks again.
Be well!

  • Jonathan
4

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