Error on the "Install the Ansible Galaxy roles" step of Trellis installation (Newbie)

I didn’t install any Python version, Python is default in my machine:

~ python
Python 2.7.10 (default, Oct 23 2015, 19:19:21)
[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.5)] on darwin

Well then…get homebrew fully setup and install (at least) python & ansible installed with brew install. Then tell us what happens.

Stay away from sudo installs/updates into your system if you can help it. Leave that to Apple.

1 Like

It’s now fixed but in a wird way. After a long digg, i finally managed to upgrade the python setuptools with this:

pip install --upgrade setuptools --user python

the wird stuff is that I got the same setuptools version (1.1.6) but now everything works fine with the Ansible Galaxy roles…

thanks for you support!


Thanks everybody for your answers!

I’ll try a few things based on your feedback and get back to you if i solve it… or not :wink:

Yes, that fixed it for me. Thanks!

Congratulations, that’s great news!

I would like to strongly suggest to you (and anyone else reading this thread) to get homebrew onto any Macintosh you plan on using Trellis with.

Updating OS X system components is a no win, zero sum game. At best, if you are lucky, you will likely need to run these upgrade commands again when a new OS update comes out. At worst, you break system functionality and sometimes are almost forced to do global/sudo installs of ansible, npm, etc.

A few years ago, I did not use homebrew and had horrible experiences with OS X updates overwriting multiple ruby packages. I would never wish a forced OS X re-install to anyone working on deadlines

1 Like


based on your feedback, after a long struggle, Google searching, reading online tutoriels and fiddling in the Terminal, i managed somehow to pass successfully that step 4 of the Trellis install!

i resolved my problem by:

  • uninstalling Python 3.5 (and Ansible which i had previously installed in it), leaving only the Python version of El Capitan
  • installing pyenv via homebrew
  • installing Python 2.7.11 and 3.5.1 via pyenv
  • setting Python 2.7.11 as global via pyenv
  • re-installing Ansible via pip in the Python 2.7.11 managed by pyenv

Once everything correctly installed, it just worked (and i learned a few tricks, still a newbie though).

Next step: configuring the WordPress sites, wish me luck :wink:


I ran into a similar issue on vagrant up, after I upgraded pip. I upgraded setuptools but was unable to upgrade asnisble. Wrote the ansible upgrade command like this and it worked fine.
sudo -H pip install --upgrade ansible --user python

It was working for me… until I install Homebrew… Now I’m stuck with this same issue, not sure how to proceed.

Do you know if the python/pip that you now have is via homebrew? You might want to start with which pip to make sure it is within a homebrew directory (/usr/local/bin/) and then follow the 3 pip list/install/freeze commands from my April 30 post. Separately, you can update all of homebrew with these three commands: brew update; brew upgrade --all; brew doctor

1 Like

Yes it’s good!

Everything is up to date.

The freeze command brings an error message :slight_smile:

Exception: Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/pip/", line 215, in main status =, args) File "/usr/local/lib/python2.7/site-packages/pip/commands/", line 317, in run prefix=options.prefix_path, File "/usr/local/lib/python2.7/site-packages/pip/req/", line 736, in install requirement.uninstall(auto_confirm=True) File "/usr/local/lib/python2.7/site-packages/pip/req/", line 742, in uninstall paths_to_remove.remove(auto_confirm) File "/usr/local/lib/python2.7/site-packages/pip/req/", line 115, in remove renames(path, new_path) File "/usr/local/lib/python2.7/site-packages/pip/utils/", line 267, in renames shutil.move(old, new) File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 300, in move rmtree(src) File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 252, in rmtree onerror(os.remove, fullname, sys.exc_info()) File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 250, in rmtree os.remove(fullname) OSError: [Errno 13] Permission denied: '/Library/Python/2.7/site-packages/ansible-'

Did you copy/paste the whole last line?
pip freeze --local | grep -v '^\-e' | cut -d = -f 1 | xargs pip install -U

That last OSError line is a concern as is referencing the OS (and not homebrew) system. I don’t even have a a thought as to a direction to point you in with that one. :confused:

Yes I did :wink:

I did a “doctor” and I have unlinked directories apparently, trying some fixes… Not sure where I’m going ^^°

Currently reading this :

So the Freeze is still bringing an error message BUT the ansible galaxy role has been installed and vagrant up is working now :slight_smile:

Maybe after a sudo pip upgrade?

I’m at a loss here. My best guess is that you have a pip-referenced package(s) that is lurking in the system library. I would probably try to

  1. Make a system backup :sweat_smile:
  2. Uninstall all homebrew-based pip installs
  3. Run those “pip freeze” commands to see if the problem is still there
  4. Reinstall the basic pip packages:
    pip install --upgrade pip setuptools pep8 passlib
  5. Run those “pip freeze” commands again and keep fingers crossed.

Gonna try this ! Thanks a lot.

Finally my vagrant up has some issues :

ERROR! Unexpected Exception: ‘TaskInclude’ object has no attribute 'has_triggered’
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

BTW it was working fine a few weeks ago, except for vault encryption.

Saturday news : I removed the Pythons in /libraries and the freeze command ran properly.
Still having the error when doing vagrant up.

Think this issue is a dupe of

It’s now all solved reverting to Ansible 2.0

This thread is about a specific Python 3 issue which has been solved. I’m closing it so others don’t keep posting about unrelated problems.