-
Notifications
You must be signed in to change notification settings - Fork 198
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
What do "present in the Mitogen importer blacklist" errors mean? #724
Comments
This part is the most important: Mitogen works by streaming package data to its clients, so if the package doesn't exist on your host machine (the "master") then it doesn't make sense for the target node to request it from the master because it doesn't exist there. Mitogen is designed to require minimal installation of packages to get stuff to work on target hosts :) Please try installing |
Thanks. I'm not a python dev so it'll take a while to dig into your recommendations. In the meantime, I looked into the symlink theory. This is what I found: Master's [defaults]
interpreter_python = /usr/bin/python3
strategy_plugins = ~/.mitogen/ansible_mitogen/plugins/strategy
strategy = mitogen_linear Master: $ which python; which python2; which python3
/usr/bin/python
/usr/bin/python2
/usr/bin/python3
$ python --version; python2 --version; python3 --version
Python 2.7.18rc1
Python 2.7.18rc1
Python 3.8.2 Remote: $ which python; which python2; which python3
/usr/bin/python
/usr/bin/python2
/usr/bin/python3
$ python --version; python2 --version; python3 --version
Python 2.7.17
Python 2.7.17
Python 3.6.9 Looks ok? |
Sorry for the late response; I thought I responded to this already :(
|
@s1113950 I have same problem. My playbook for reproducing: - hosts: all
become: true
tasks:
- name: step1
ansible.builtin.pip:
name: docker
executable: pip3
- name: step2
community.docker.docker_host_info: Error:
Important moment: playbook is restarted without errors. But, I found workaround. It need to reset connection between step 1 and step2. Like this: - hosts: all
become: true
tasks:
- name: step1
ansible.builtin.pip:
name: docker
executable: /bin/pip3.6
- name: reset ssh connection
ansible.builtin.meta: reset_connection
- name: step2
community.docker.docker_host_info: Info about my system: Python:
Docker package:
|
Docker is installed
Still mitogen fails with
Obviously imports just fine in the REPL.
|
FWIW I was also seeing a similar error when running a task like: community.general.docker_container:
name: sphinx
image: macbre/sphinxsearch:3.4.1
state: started
restart_policy: unless-stopped
container_default_behavior: no_defaults
user: "{{ getent_passwd['sphinx'].1 }}:{{ getent_passwd['sphinx'].2 }}" resulting in:
However! If I change my playbook strategy back to
So (at least in my case) the "Mitogen importer blacklist" error message was misleading (my actual problem was that I'd run |
in my case i get a similar error but using the linear strategy makes the problem go away ... any hint why this is not working ? |
How did you end up solving this problem? |
ubuntu 20.04
ansible 2.9.6
python 3.8.2
mitogen beta 0.2.10 2020-05-16 (also tried 0.2.9)
I often get similar error to the one below. They generally say something like
In this particular case, I'm checking something on localhost:
Error:
It works when mitogen isn't enabled.
The text was updated successfully, but these errors were encountered: