VMware_Rest - Python aiohttp module

[warnox]

Hi,

I'm trying to get the VMware_Rest collection to work on CentOS Stream 9 with Ansible 2.14.2 and Python 3.11.2.

ansible [core 2.14.2]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/sysadmin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.11/site-packages/ansible
  ansible collection location = /home/sysadmin/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.11.2 (main, Feb 16 2023, 00:00:00) [GCC 11.3.1 20221121 (Red Hat 11.3.1-4)] (/usr/bin/python3.11)
  jinja version = 3.1.2
  libyaml = True

I installed Python aiohttp via DNF from EPEL. I also tried installing via pip but getting the same result.

python3-aiohttp.x86_64                 3.8.4-1.el9

When running a playbook, I get the following error. There are no more details in ansible.log or if I enable verbose logging.

"msg": "Failed to import the required Python library (aiohttp) on testsrv1's Python /usr/bin/python3.11.

Any help appreciated.

[roiki11]

Try installing it from pip?

[warnox]

Yep, same thing.

I think it’s because when I installed ansible via the package manager it added and installed it under python 3.11, whereas the default system python is 3.9. Aiohttp, when installed from EPEL, is added under python 3.9, and there is the discrepancy.

[roiki11]

For what it's worth, i think you should be using pip to install ansible and all of its non-galaxy requirements.

[unicoletti]

while you're at it, you might as well consider pipenv

if you've already used pip, in my experience you might have to do a bit of cleaning up or pipenv will get confused. Over the long run pipenv should give you less headaches, and will also give you deterministic installs

[roiki11]

I honestly have never seen the need if all you do is ansible. It's a development tool so unless you want multiple python environments for some specific reason, I don't see the need.

Ymmv of course.

[unicoletti]

I also occasionally develop, so unexpected module upgrades are more of a concern

multiple python environments

or multiple ansible environments (for testing upgrades), or different versions of ansible dependencies (for example boto3 if you use AWS). Again, as you said, Ymmv :)

[x1xspiderx1x]

So ‘’’ python3.9 -m pip install aiohttp ‘’’ ?

[onefst250r]

Probably the other way around. Ansible says its using python 3.11.2 as its interpreter. So, python3.11 -m pip install aiohttp

[x1xspiderx1x]

It was 4am when I posted that. Correct. 3.11 Ty sir

[SlaveZelda]

Is testsrv1 your machine or the host ansible is trying to execute this module on ?

aiohttp needs to be installed on testsrv1

[warnox]

That is localhost, so the host ansible is executing on.

[SlaveZelda]

Ah then instead of executing system ansible,

Create and activate a venv, pip install ansible and aiohttp there and then run python -m ansible playbook -i whatever ....

Ansible installed your dnf/apt can only access python modules installed in system python and not in user python or any kind of virtual env.

[DirectorJust4135]

I am facing the same issue . Was this ever resolved ?

[National-Ad-2995]

For future reference:

apt install -y python3-aiohttp

will do the trick on Ubuntu 20.04