enigmatic traceback

[Diogene Laerce]

Hi,

I got this traceback when trying to run a playbook with ansible 1.8 on
Debian Wheezy :

Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 324, in <module>
sys.exit(main(sys.argv[1:]))
File "/usr/bin/ansible-playbook", line 264, in main
pb.run()
File "/usr/lib/pymodules/python2.7/ansible/playbook/__init__.py", line
313, in run
play = Play(self, play_ds, play_basedir, vault_password=self.vault_password)
File "/usr/lib/pymodules/python2.7/ansible/playbook/play.py", line 165,
in __init__
self._tasks = self._load_tasks(self._ds.get('tasks', []), load_vars)
File "/usr/lib/pymodules/python2.7/ansible/playbook/play.py", line 598,
in _load_tasks
loaded = self._load_tasks(data, mv, default_vars, included_sudo_vars,
list(included_additional_conditions), original_file=include_filename,
role_name=new_role)
File "/usr/lib/pymodules/python2.7/ansible/playbook/play.py", line 606,
in _load_tasks
role_name=role_name
File "/usr/lib/pymodules/python2.7/ansible/playbook/task.py", line 69,
in __init__
if x in utils.plugins.module_finder:
File "/usr/lib/pymodules/python2.7/ansible/utils/plugins.py", line 186,
in has_plugin
return self.find_plugin(name) is not None
File "/usr/lib/pymodules/python2.7/ansible/utils/plugins.py", line 175,
in find_plugin
for i in self._get_paths():
File "/usr/lib/pymodules/python2.7/ansible/utils/plugins.py", line 138,
in _get_paths
ret.extend(self._get_package_paths())
File "/usr/lib/pymodules/python2.7/ansible/utils/plugins.py", line 94,
in _get_package_paths
m = __import__(self.package)
ImportError: No module named modules


Does anyone know what this is about ?

Thank you, regards

--
“One original thought is worth a thousand mindless quotings.”
“Le vrai n'est pas plus sûr que le probable.”

Diogene Laerce

[Matt Martz]

How did you install 1.8?  Ansible now uses sub modules for a few paths, so you need to make sure you follow:

You can find instructions here for a variety of platforms. If you decide to go with the development branch, be sure to run "git submodule update --init --recursive" after doing a checkout.

--

Matt Martz
@sivel
sivel.net

[Michael DeHaan]

FWIW Matt - Ansible will produce more human readable errors when a submodule isn't checked out.

But yeah, I'm curious how this was installed.

--
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/CAD8N0v899-8r_J4WNDhipcFP7LgU9Y4d8Qt_rFL0Q8vkZoGSPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Diogene Laerce]

Hi,

On 11/01/2014 03:08 PM, Matt Martz wrote:
> How did you install 1.8? Ansible now uses sub modules for a few paths,
> so you need to make sure you follow:
>
> You can find instructions here

> <http://docs.ansible.com/intro_getting_started.html> for a variety of

> platforms. If you decide to go with the development branch, be sure to
> run "git submodule update --init --recursive" after doing a checkout.

I installed it with the "make deb" feature.

So I uninstalled it, recloned, ran the given command and remade the deb
package : it now works.

Thank you

[Michael DeHaan]

Doing "make deb" without getting the latest submodules first would leave some things out, yes.

(I'm still curious why it tracebacked versus giving you the "can't find modules" friendly message)

[Dmitry Zelenkovsky]

Guys, please make it throw something better then python exception! I've spent damn half an hour trying to run my playbooks ;(