Okay, so my error was very very stupid. Everything was correct, but I was executing the playbook as such ‘sudo ansible-playbook xxxxx’ and believe since was sudo’ing, I was losing the environment variables that were previously set. Either way, after running it without sudo, it worked just fine.
On Friday, March 28, 2014 7:53:43 AM UTC-4, Jason Edelman wrote: > > Hi All, > > I keep getting an "ImportError: No module named" when I try and run a > playbook using a custom python module (that is trying to import a 3rd party > python package). > > Few things: > - importing the 3rd party package works from the python shell from all > over my machine. > - PYTHONPATH seems to be correct, hence, importing the package works > - using the hacking test script also does NOT reproduce the error. So > this works fine. > - I've tried ansible_python_interpreter=/usr/bin/python2.7 > - Seem to have removed py3 just by using rm > - using 'connection: local' so the target host is "my host" also executing > the playbook > > I'm a new guy, so help me not leave any stone unturned :). Don't assume > anything please! > > Thanks in advance. > > -Jason > > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a4e017d4-03f5-411e-b663-45f7424866be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
