What happend? Boto not found? sys is not defined?

[Barry Kaplan]

I've been running these playbooks with ansible 1.9.1 and 1.9.2 for weeks now on this same workstations. Now all of the sudden I get the below error. 

I have no idea what could have triggered this. Anybody seen this before?

failed: [localhost] => {"failed": true, "parsed": false}

failed=True msg='boto required for this module'
Traceback (most recent call last):
  File "/Users/bkaplan/.ansible/tmp/ansible-tmp-1433560234.51-65949177742337/ec2_group", line 114, in <module>
    sys.exit(1)
NameError: name 'sys' is not defined

[Barry Kaplan]

So this is only on OSX. On linux the same project runs fine.

[Barry Kaplan]

I found this issue https://github.com/ansible/ansible-modules-core/issues/994. And tried:

export PYTHONPATH="/usr/local/lib/python2.7/site-packages"

This fixed the problem on osx. But I still can't fathom what happened to cause this to be required.

[Brian Coca]

did you install ansible via homebrew?

> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/0ddaf962-c7a9-4737-9cde-7d0d7627cad0%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



--
Brian Coca

[Barry Kaplan]

On Saturday, June 6, 2015 at 9:08:36 AM UTC+5:30, Brian Coca wrote:

did you install ansible via homebrew?

Hmm, I really don't remember. I could have been via pip. But I'm guessing that I did whatever the install the instructions said because when I first installed ansible (and started using ansible) was just 4 or 5 weeks ago.

(And I must say, that in 4 or 5 weekends, I have completely rebuilt 2 years of chef work. Not only rebuilt, but everything is way way way way cleaner. No more chefdk, berks, uploads, chef server errors, complex resources-defs and impls, constant gem conflicts -- I could rant for hours. And on top of that I now create all the resources that our systems run on: aws security groups, elb, ebs, route53, etc. So I can blow away and recreate entire sub-stacks at will. My life is has been improved tremendously by ansible.)