Hmm, that’s weird. Try: sudo pip install ansible==2.0.0.2
Or you can always try installing the 2.0.0.2 version with the Tarball package: http://releases.ansible.com/ansible/
Got the compat.six error on ansible 1.9.4, which, seems expected. Also got an error about setuptools when I tried updating ansible with the upgrade flag. Using sudo pip install ansible== and specifying the version works every time
Since the update, I can’t get Trellis to successfully deploy to development, staging or production.
The error I get running vagrant up --provision is:
ERROR! Unexpected Exception, this is probably a bug: No module named six
to see the full traceback, use -vvv
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
As far as I can tell, I have six installed.
Using apt:
$ dpkg -l | grep six
ii python-six 1.10.0-3 all Python 2 and 3 compatibility library (Python 2 interface)
ii python3-six 1.10.0-3 all Python 2 and 3 compatibility library (Python 3 interface)
Using pip:
$ pip list | grep six
six (1.10.0)
I stumbled on this issue on GitHub. Not sure if it is related.
I’d suggest using pip to downgrade to Ansible 2.3.2.0: pip install ansible==2.3.2.0
Trellis compatibility with Ansible 2.4 has been proposed but not yet reviewed nor merged. If you’re inclined to test it, your feedback would be welcome!
Brew has lovingly “updated” python’s default install and sync locations on MacOS from past behavior, which has caused several cluster****s as far as Path is concerned on my system. (They had a legit reason for doing this, it just sucks).
So I’m not positive, but it looks like my python version is several updates behind Ansible’s. I’m not sure if I’m reading that correctly.
…
Fail: Setting path correctly w/ python at 2.7.14 did not fix this
Had the same issue: reinstalled virtualbox via brew and then clicked “Allow” In System Preferences -> Security & Privacy when it appears. Also had to kill all the running instances even after removing VirtualBox app from Applications. ps aux helps with that.
Then sadly after changing some settings and provisioning (or destroy + vagrant up again), another error pops up sometimes, but otherwise it seems the above fixed it for me on os x:
ERROR! Unexpected Exception, this is probably a bug: 'PlaybookCLI' object has no attribute 'options'
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
hmmph, so annoying to run into errors one after another indeed. Haven’t been able to get trellis working for months
I was also running into that same exception ‘PlaybookCLI’ object has no attribute ‘options’ when upgrading to the latest trellis v1.2.0. I had to revert the ansible version to v2.5.3 after trying out v2.8.5 and v2.7.12 respectively.
Yeah I see the issue is in my Ansible version indeed - if I properly read the requirements from https://github.com/roots/roots-example-project.com I would have noticed before: it says Ansible should be 2.5.3-2.7.5. Working with Trellis updated to latest master - 1.2.0!
Thanks guys, @crypticsoft too for chiming in
