From 04ac053bfd9c5ca500f3c60681d51a0902e50637 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Wed, 16 Nov 2022 17:07:20 +0900 Subject: [PATCH] Update comments about python versions used in sanity checks ... to explain why we need these more clearly and precisely. Change-Id: I9acffef0d85ccb0dfc2c5ebaba7f1c9c72c8435e --- zuul.d/layout.yaml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/zuul.d/layout.yaml b/zuul.d/layout.yaml index 0a6f931..6fcdbba 100644 --- a/zuul.d/layout.yaml +++ b/zuul.d/layout.yaml @@ -5,7 +5,11 @@ parent: tox vars: tox_envlist: sanity # dynamic tox env added by tox-ansible - # we want to run sanity only on py3.10 instead of implicit 2.6-3.9 range + # We need to use the proper python version depends on the Ansible + # version (For example python 3.10 requires Ansible >=2.13). As we pin + # Ansible version for sanity environemnt in tox.ini, we pin python + # version here. Python 3.10 is now the default Python version in Jammy + # and we need to revisit this when we migrate this job to a new version. tox_extra_args: -- --python 3.10 - job: @@ -14,8 +18,8 @@ parent: tox vars: tox_envlist: units # dynamic tox env added by tox-ansible - # we want to run sanity only on py36 instead of implicit 2.6-3.9 range - # tox_extra_args: -- --python 3.6 + # Now we do not pin ansible in the unit environment so we do not pin + # Python version explicitly here. - job: name: zuul-ansible-role-collect-logs