Hi all, A quick question as I'm slightly knee-deep in troubleshooting an upgrade to Ansible 2.7, but did the way searching for python libraries / site-package directories change, specifically with regard to the Azure cloud modules?
As a quick test, I'm in a virtualenv with Ansible 2.7 installed and ansible[azure] included. If I try to use azure_rm_resourcegroup_facts in a playbook, I get "Do you have packaging installed? Try pip install packaging" I do have packaging installed, as I can open python REPL and type 'import packaging' and see packagine.__file__ pointing to the site-packages under the virtualenv OK. If I precede running ansible-playbook with PYTHONPATH, e.g. PYTHONPATH=/root/plays/ansible-azure/lib/python2.7/site-packages ansible-playbook test.yml then the Azure module works fine. Unfortunately while this might be a quick fix for command line Ansible (declare PYTHONPATH in some shell vars file), the actual problem I need to resolve is inside Ansible Tower and so I'm unclear what I would need to do to make Ansible Tower look in the right place for libraries. The point of this slightly rambly post is to work out whether this was an unannounced change in module functionality in 2.7 or whether I've missed something important off the changelogs and now need to update how python package lookups are handled. Thanks for reading! Andy -- 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/48e17ab4-f83b-4877-83a6-5d337c6d05ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
