Bug 2196539

Summary:	ansible-core fails to build with Python 3.12: add support for Python 3.12
Product:	[Fedora] Fedora	Reporter:	Tomáš Hrnčiar <thrnciar>
Component:	ansible-core	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	kevin, maxwell, mhroncok, moi, thrnciar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ansible-core-2.15.1-1.fc39	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-03 18:39:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2135404

Description Tomáš Hrnčiar 2023-05-09 12:41:24 UTC

ansible-core fails to build with Python 3.12.0a7.

+ /usr/bin/python3 bin/ansible-test units --local --python-interpreter /usr/bin/python3
This version of ansible-test cannot be executed with Python version 3.12.0. Supported Python versions are: 3.9, 3.10, 3.11

https://docs.python.org/3.12/whatsnew/3.12.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05900503-ansible-core/

For all our attempts to build ansible-core with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/ansible-core/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.12:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/

Let us know here if you have any questions.

Python 3.12 is planned to be included in Fedora 39. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.12.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Maxwell G 2023-05-12 02:13:46 UTC

Thank you for working on the Python 3.12 prep, Tomáš and Miro!

ansible-core hardcodes the Python versions supported by ansible-test in https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_util/target/common/constants.py.

We can temporarily patch this out like we did for Python 3.11 [1] to get `ansible-test units` to work in the RPM build. However, I want to get ansible-core 2.16 which will officially support Python 3.12 into the Fedora 39 GA for the reasons I outlined in [2]. The first beta of ansible-core 2.16 releases on 2023-09-25 which is ~ a week and a half before the Fedora 39 final freeze on 2023-10-03. The timing is not great, but I think this is the best choice for our users. I don't want to go against upstream and ship 2.15 which doesn't support Python 3.12. The controller portion and ansible plugins should work with minor adjustments, but ansible-test is picky about Python versions (especially `ansible-test sanity`) and shipping it like this will cause problems for plugin developers.


[1] https://src.fedoraproject.org/rpms/ansible-core/c/c175ef7d47e8d305dd747829787acc4f72205c3d?branch=rawhide
[2] https://pagure.io/fesco/issue/2886

Comment 2 Maxwell G 2023-05-12 02:29:47 UTC

Ah, I now see you linked an upstream issue. I probably should've read that first...

Comment 3 Maxwell G 2023-06-13 22:25:02 UTC

https://src.fedoraproject.org/rpms/ansible-core/pull-request/27

Comment 4 Fedora Update System 2023-07-03 18:33:10 UTC

FEDORA-2023-f1c810932f has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f1c810932f

Comment 5 Fedora Update System 2023-07-03 18:39:09 UTC

FEDORA-2023-f1c810932f has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.