Otto is correct - I believe this is an issue with Ansible 2.7 using Python 3, which ends up causing some trouble. Try with Ansible 2.6.5. It looks like you're using Homebrew (which is what our README recommends, so that's not surprising), and you can use some combo of the following commands: # get info on what you have brew info ansible or brew list ansible --versions # fresh install 2.6.5 brew install ansible@2.6.5 # switch already installed versions brew switch ansible 2.6.5
If that doesn't end up working with Homebrew (might not have that version), then uninstall and use pip brew uninstall ansible I personally installed it with pip a while back, which works. sudo pip install ansible=2.6.5 Hope this helps. And we'd very much appreciate it if you would share your findings so we can update the documentation accordingly. Best, Mike Miklavcic On Fri, Feb 1, 2019 at 10:09 AM Otto Fowler <ottobackwa...@gmail.com> wrote: > I don’t think the issue is in the VM though. > > "File > "/usr/local/Cellar/ansible/2.7.6/libexec/lib/python3.7/site-packages/ansible/plugins/action/normal.py", > line 46, in run” > > that is a home-brew path. > > FWIW, https://github.com/apache/metron/pull/1261 is a PR to build the > full dev vm using docker to do the building, so that your local env isn’t > such a pain. > Maybe you can tray that out and see if it works? > > > > On February 1, 2019 at 11:33:44, Ryan Sommers (ry...@rpsommers.com) wrote: > > File > "/usr/local/Cellar/ansible/2.7.6/libexec/lib/python3.7/site-packages/ansible/plugins/action/normal.py", > line 46, in run > >
