Error running drupal playbook directly on Ubuntu 20.04

I am using ansible 2.10.3, and running the playbook with the command:

ansible-playbook -c local -i 'localhost,' playbook.yml

Then I get:

PLAY [all] ************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ************************************************************************************************************************************************************************************
[WARNING]: Unhandled error in Python interpreter discovery for host localhost: '<' not supported between instances of 'str' and 'int'
fatal: [localhost]: FAILED! => {"ansible_facts": {}, "changed": false, "failed_modules": {"ansible.legacy.setup": {"ansible_facts": {"discovered_interpreter_python": "/home/static/.pyenv/shims/python3.7"}, "failed": true, "module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1, "warnings": ["Platform linux on host localhost is using the discovered Python interpreter at /home/static/.pyenv/shims/python3.7, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible/2.10/reference_appendices/interpreter_discovery.html for more information."]}}, "msg": "The following modules failed to execute: ansible.legacy.setup\n"}

PLAY RECAP ************************************************************************************************************************************************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

After reading the mentioned documentation I couldn’t really figure out what was the problem here.

BTW @geerlingguy congratulations for the great work, keep on!

[geerlingguy]

It looks like if you’re trying to run this against localhost—e.g. your local workstation—you would need to provide a sudo password so the playbook can configure everything.

I would recommend running the example against a VM or something first, before applying all the changes locally, if you’re running from your normal workstation.

But in any case, to provide a sudo password, you can use the -k option.

[staticdev]

@geerlingguy I did what you told me. You were correct, I installed Python 3.9 with pyenv and Ubuntu 20.04 cames with 3.8. The problem is that the installed python3-apt just works on the system installed python (you check it with import apt).

The “solution” is adding the path to original system interpreter to override the one detected by ansible with ansible_python_interpreter=/usr/bin/python3. Anyhow, I also think there is a problem with ansible 2.10 either with the detection of the used interpreter or, at least, this message error telling me to install python3-apt.