ansible-test sanity failing with "No module named 'jinja2'"

[geerlingguy]

SUMMARY

In the Kubernetes collection's CI tests, the sanity check, which uses ansible-test sanity --docker -v --color --python 3.6, started failing with the following error:

ERROR: Command "importer.py" returned exit status 1.
>>> Standard Error
Traceback (most recent call last):
  File "/root/ansible/ansible_collections/community/kubernetes/tests/output/.tmp/sanity/import/minimal-py36/bin/importer.py", line 447, in <module>
    main()
  File "/root/ansible/ansible_collections/community/kubernetes/tests/output/.tmp/sanity/import/minimal-py36/bin/importer.py", line 51, in main
    from ansible.utils.collection_loader import AnsibleCollectionLoader
  File "/root/ansible/lib/ansible/utils/collection_loader.py", line 15, in <module>
    from ansible import constants as C
  File "/root/ansible/lib/ansible/constants.py", line 12, in <module>
    from jinja2 import Template
ModuleNotFoundError: No module named 'jinja2'

Nothing in the collection has changed in the past week, and no runs failed until this morning's CI run, so it seems something committed to ansible/ansible devel has caused this failure.

ISSUE TYPE

• Bug Report

COMPONENT NAME

ansible-test

ANSIBLE VERSION

devel (as of this morning)

CONFIGURATION

N/A - defaults

OS / ENVIRONMENT

Linux

STEPS TO REPRODUCE

1. Clone kubernetes collection repo
2. Install Ansible @ devel
3. Run ansible-test sanity --docker -v --color --python 3.6

EXPECTED RESULTS

Tests should pass, as they have for the past few weeks.

ACTUAL RESULTS

Test fail, with the message in this issue's summary.

[ansibot]

Files identified in the description:

• bin/ansible-test

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help