New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Route53 - ModuleNotFoundError: No module named 'ansible_collections' Error #794
Comments
should this also happen with any collection?
please confirm that any collection support is still broken in 522085a |
yes, w/o mitogen collections work great |
I too, am experiencing this. Using ansible 2.10.6, Mitogen 0.3.0rc1. Attempting to use
|
out of curiosity, are you running ansible in a python virtual env? I am, and I'm wondering if mitogen is looking in the wrong spot for the collection? |
hmmm good point, yes I believe I'm running a python 3.8 that's installed by anaconda |
I’m running a 3.7, but the venv is in /opt/venv/
I wonder where mitogen is looking for collections?
…On Feb 5, 2021, 2:45 PM -0500, Chad Cravens ***@***.***>, wrote:
hmmm good point, yes I believe I'm running a python 3.8 that's installed by anaconda
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
i'm running 3.8 installed as regular system binary |
@badfiles @codefriar It's possible Mitogen is looking in the wrong place then. It uses |
yep, setting https://docs.ansible.com/ansible/latest/reference_appendices/config.html#collections-paths |
@s1113950 Is it possible to auto search the folder Without mitogen it works w/o error, with mitogen it complains that it cannot find the collection. Adding: |
It should be possible I think. Mitogen finds collections via the Ansible function |
I'm also affected by the inability to find any collection (including those bundled) when installed in a venv. I noticed the collections-scan-sys-path (default True) which allows for this, I presume, but fails with Mitogen installed (0.3.0rc1). Having it to point to an installation-specific path (different for every venv) feels very wrong. Also, it doesn't work for me when using e.g.
still gives me the
This fails as if
Update: I managed to solve this issue by upgrading the |
Any updates? |
Which version of Ansible are you running?
ansible 2.10.3
config file = ansible.cfg
configured module search path = ['/Users/ccravens/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/Cellar/ansible/2.10.4/libexec/lib/python3.9/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.9.1 (default, Dec 10 2020, 10:36:41) [Clang 11.0.0 (clang-1100.0.33.17)]
Is your version of Ansible patched in any way?
No... Not that I know of. I did install the route53 with galaxy:
ansible-galaxy collection install community.aws
https://docs.ansible.com/ansible/latest/collections/community/aws/route53_module.html
Are you running with any custom modules, or
module_utils
loaded?No
Have you tried the latest master version from Git?
Yes, both
master
andv0.3.0-rc.0
Do you have some idea of what the underlying problem may be?
None, but I think it may be due to Ansible 2.10
Mention your host and target OS and versions
Mac OSX - running
local
Mention your host and target Python versions
Same as above, running
local
If reporting a crash or hang in Ansible, please rerun with -vvv and include
If reporting any kind of problem with Ansible, please include the Ansible version along with output of "ansible-config dump --only-changed"
The text was updated successfully, but these errors were encountered: