5f1069ba9a
ansible-test seems to take the latest ansible-core by default, even if we push upper/lower constraints in the requirements.txt or test-requirements.txt. Pushing the constraint directly in the tox.ini, for the "sanity" testenv, seems to do the trick, as we're testing against an ansible version we actually support, instead of the latest (2.13 today). This patch also takes the opportunity to remove unwanted warnings (ansible.cfg deprecated options), as well as ensuring the ignored content for `ansible-test' doesn't raise any warning. Closes-Bug: #1976251 Change-Id: I596aecd71ebe7d8a747ab8e6d05766f70dd78f1d
13 lines
398 B
INI
13 lines
398 B
INI
[defaults]
|
|
gathering = smart
|
|
retry_files_enabled = False
|
|
callbacks_enabled = profile_tasks
|
|
|
|
# Attempt to load custom modules whether it's installed system-wide or from a virtual environment
|
|
roles_path = roles:$VIRTUAL_ENV/share/ansible/roles:$VIRTUAL_ENV/usr/local/share/ansible/roles:$VIRTUAL_ENV/usr/share/ansible/roles
|
|
|
|
# Required by infrared
|
|
host_key_checking = False
|
|
forks = 500
|
|
timeout = 300
|