Default python 3.9 of debian 11 crash the test playbook.

Poetry installation during the ansible "test.playbook.yml" is crashed because of an error inside the default Python version installed on rotated lab :

Here is the details :

Traceback (most recent call last): File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.9/runpy.py", line 87, in _run_code exec(code, run_globals) File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/main.py", line 163, in File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/main.py", line 159, in run File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/main.py", line 18, in run File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/init.py", line 31, in cli_run File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/init.py", line 49, in session_via_cli File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/init.py", line 82, in build_parser File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/plugin/creators.py", line 24, in init File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/plugin/creators.py", line 31, in for_interpreter File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/plugin/base.py", line 45, in options File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/plugin/base.py", line 24, in entry_points_for File "/tmp/poetry-installer5dz4f3zl/virtualenv.pyz/virtualenv/run/plugin/base.py", line 24, in File "/usr/lib/python3.9/importlib/metadata.py", line 79, in load return functools.reduce(getattr, attrs, module) AttributeError: module 'virtualenv.create.via_global_ref.builtin.cpython.mac_os' has no attribute 'CPython2macOsFramework'

Traceback:

File "", line 923, in main File "", line 560, in run File "", line 581, in install File "/usr/lib/python3.9/contextlib.py", line 117, in enter return next(self.gen) File "", line 653, in make_env File "", line 639, in make_env File "", line 341, in make File "", line 365, in run

As pyenv is not installed yet, we did the installation step manually as a workaround. Using v3.11.8 as global python version show us that the problem is indeed on the default version side.