2023-02-08 03:36:42.121587 | ERROR! unexpected parameter type in action: <class 'ansible.parsing.yaml.objects.AnsibleSequence'> 2023-02-08 03:36:42.121599 | 2023-02-08 03:36:42.121611 | The error appears to be in '/var/lib/zuul/builds/e8389a873fb545e68679e27a1276860d/untrusted/project_2/opendev.org/openstack/openstack-zuul-jobs/playbooks/tox/py27.yaml': line 13, column 7, but may 2023-02-08 03:36:42.121624 | be elsewhere in the file depending on the exact syntax problem. 2023-02-08 03:36:42.121637 | 2023-02-08 03:36:42.121649 | The offending line appears to be: 2023-02-08 03:36:42.121661 | 2023-02-08 03:36:42.121672 | tasks: 2023-02-08 03:36:42.121684 | - name: Install Python 2.7 2023-02-08 03:36:42.121697 | ^ here
~~~
On 2023-02-07 09:21:56 -0800 (-0800), Dariusz Smigiel wrote:
> Recent change [1] to remove python27 from images caused issues across
> jobs still using python 2.7 There are a lot of projects failing due to
> that. [2] The solution is to update bindep.txt [3]
> The fix was discussed with the #opendev team and can be summarized as
> follows. [4]
>
> ```
> 15:37 <clarkb> I think we have ~3 options: A) revert/or readd
> python2-dev installs B) ask projects to fix their broken bindep.txts
> (something we've asked for for years at this point) or C) update -py27
> jobs to explicitly install python2 for you
> ```
[...]
We also merged https://review.opendev.org/873020 about twenty
minutes ago, so as of 22:12:13 any jobs inheriting from
openstack-tox-py27 will automatically install the python and
python-dev (old Python 2.7) packages.
But definitely still put Python interpreters in your bindep.txt
files, they're useful if for no other reason than to indicate to
anyone looking at the file that your project needs those.
--
Jeremy Stanley