zuul/zuul
Code Issues Proposed changes

Add upgrade note about ansible_python_interpreter

Browse Source 
Under ansible 2.8, ansible_python_interpreter now defaults to auto. This
could break some users playbooks. Lets add an upgrade note.

Change-Id: Ia7c36ed364f553e4c30347c72cde59879f5ac5d9
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This commit is contained in:
Paul Belanger 2019-12-10 14:57:20 -05:00
parent 15afed554e
commit 5c1a941f8f
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin/components.rst
View File

@ -821,6 +821,8 @@ To enable or disable running Ansible in verbose mode (with the
``-vvv`` argument to ansible-playbook) run ``zuul-executor verbose``
and ``zuul-executor unverbose``.
.. _ansible-and-python-3:
Ansible and Python 3
~~~~~~~~~~~~~~~~~~~~

6
releasenotes/notes/ansible-2.8-default-version-43754b72b3dd2897.yaml
View File

@ -3,6 +3,12 @@ upgrade:
- |
The default version of Ansible used by Zuul jobs has been changed to 2.8.
See :attr:`job.ansible-version` for more information.
- |
As a result of switching to Ansible 2.8, it is possible for the
ansible_python_interpreter version of your nodeset to change to 'auto'.
This could result in your jobs now running under a different version of
python than prior to this release. See :ref:`ansible-and-python-3` for
additional info.
- |
Ansible 2.6 for Zuul jobs has been marked deprecated and will be removed in
a future release.