On Sun, 2025-03-02 at 09:19 +0100, Johannes Kastl wrote:
Hi Martin,
On 28.02.25 16:57 Martin Wilck via openSUSE Factory wrote:
On Fri, 2025-02-28 at 14:30 +0100, Stefan Seyfried via openSUSE Factory wrote:
Probably for those who really cannot update that quickly, there are also ansible-core-2.17 and ansible-10 packages around.
... which can't be used to administer target systems with python 3.6. Which means all of SLE/Leap 15, basically. (For 15.6 and newer it might be possible to set ansibly_python_interpreter to python311, haven't tried - but for users of ansible that implies a chicken-and-egg problem, as python311 isn't necessarily installed in the first place).
That was the reason ansible-core-2.16 was introduced into Factory, to ease the transition.
I know, thanks again for that.
But it always had a limited lifetime. Now that it" does no longer get updates it might no longer be safe to use.
According to the support matrix [1] the EOL of 2.16 is May 2025, although it hasn't been receiving security updates since November 2024. I don't fully understand the logic behind that. Ansible 2.16 was special in general, because it's "long term release" [2], and for SUSE in particular, because it was the last release to support python 3.6. While you're of course free and welcome to do it, I don't see a strong case for maintaining ansible-core 2.17 in Factory.
ansible_python_interpreter is exactly the way to go. You can even do that with Ansible.
Here is an example from one of my vagrant setups, using Leap 15.6 and bootstrapping python3.11:
https://github.com/johanneskastl/nfs-ganesha_on_k3s_using_vagrant_libvirt_an...
Thanks a lot, this is helpful. It isn't perfect for SLE because it won't work for SLE <= 15.4 and it requires the python3 module to be enabled, but I suppose we can handle the remaining cases with ansible- navigator. Thanks Martin [1] https://docs.ansible.com/ansible/devel/reference_appendices/release_and_main... [2] https://docs.ansible.com/ansible/latest/reference_appendices/release_and_mai...