Ansible failed to complete successfully

trellis
21

I’ve found this to be good nudge to actually update Trellis on these sites…

22

Thats for the suggestion to downgrade to 2.3.2.0, this fixed it for me too.

1 Like
23

Welp,

I guess I’ll dump my troubleshooting here since I have now joined this error boat.

TL:DR - Skip to bottom ====

Updates to High Sierra (because I’m a masochist)
Same exact error

trellis/lib/trellis/plugins/filter/filters.py", line 8, in <module>
from ansible.compat.six import string_types
ImportError: No module named six

Digging into that file, this appears to be the specific offending line

from ansible.module_utils.six import iteritems

This seems like it could be an issue

python --version
Python 2.7.10
trellis casa$ ansible --version
ansible 2.4.2.0
  config file = /Users/casa/Documents/atom/Sites/AbilityDriven/trellis/ansible.cfg
  configured module search path = [u'/Users/casa/.ansible/plugins/modules', 
  u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.14 (default, Sep 25 2017, 09:53:22) [GCC 4.2.1 Compatible 
Apple LLVM 9.0.0 (clang-900.0.37)]

  1. First thing I did was reinstall Ansible… No cigar

  2. 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.

…

  1. Fail: Setting path correctly w/ python at 2.7.14 did not fix this

=====================

Oh snap,

@swalkinshaw
@ben thoughts?

24

Derp city, somehow I still had old trellis code in my project. Updated to

newest version of Trellis resolved issues.

25

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 :slight_smile:

26

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.

1 Like
27

The PlaybookCLI error only happens in one situation: you’re using Ansible 2.8.x and do not have a recent Trellis version with Ansible 2.8 support.

If you get that error after upgrading successfully to https://github.com/roots/trellis/releases/tag/1.2.0 then please open an issue.

1 Like
28

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

1 Like
29

I’m also locking this thread now. It’s been going on way too long and evolved into many unrelated issues to the original post.

1 Like