I am in a pickle.
I always tried to keep up with the Ansible Core releases and for a while I was successful. We are a RedHat shop and still have production workloads on RHEL 7.
Due to that, I am stuck on Ansible Core 2.16. I doubt it I am the only one in this situation so I am wondering if anybody else is having the same issue.
If so, what was your solution? Core 2.16 will be EOL in May, so I am kinda freaking out at this point.
Is there anyone out there able to successfully use ansible core > 2.16 and have target nodes on RHEL 7?
RHEL 7 end of life was June of 2024. I’m aware Red Hat provides extended lifecycle support, not sure if that also includes system supplied versions of Ansible. It might make more sense to ask RedHat rather than the community for their thoughts since you’re already paying them for support and they also manage Ansible.
If you want an opinion, you’ll be using an out-of-support version of Ansible to manage an out-of-support version of RedHat, oh well. Make a case to your security team to compel app owners to upgrade their apps to run on newer OSes.
Unfortunately, that’s where most likely we’ll end up: a EOL ansible control node to control the EOL Rhel7 servers.
I was just curious to see if anyone got some kind of workaround
It boils down to Python version available on RHEL 7. By default it is Python 2.7 which ansible-core 2.16+ cannot work on. If you can install a supported version of Python on both control nodes and end hosts, and make Ansible use it, then you can extend RHEL 7 support to newer versions of Ansible.
On the other hand, ansible-core 2.16 EOL is not the EOL for you . It just means that ansible-core 2.16 will not receive bug fixes any more. If there are no bugs bothering you, there is nothing preventing you to use EOL version of Ansible to handle EOL versions of Python and distros like RHEL 7. Unless you have some strict corporate policy? But if that was the case, you wouldn’t be having any RHEL 7 right now, right?
. It just means that ansible-core 2.16 will not receive bug fixes any more. If there are no bugs bothering you, there is nothing preventing you to use EOL version of Ansible to handle EOL versions of Python and distros like RHEL 7. Unless you have some strict corporate policy? But if that was the case, you wouldn’t be having any RHEL 7 right now, right?