Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine ramifications of migrating to Ansible 10.0 #481

Open
artis3n opened this issue Jun 17, 2024 · 4 comments
Open

Determine ramifications of migrating to Ansible 10.0 #481

artis3n opened this issue Jun 17, 2024 · 4 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@artis3n
Copy link
Owner

artis3n commented Jun 17, 2024

Ansible 10.0 (released June 2024) deprecates support for Python 2.7 and 3.6, which breaks many of the older distros (#478 ) tested on this role, but are still supported by Tailscale. https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_10.html

Removed Python 2.7 and Python 3.6 as a supported remote version. Python 3.7+ is now required for target execution.

Have to figure out how we want to handle that inside this role. Eventually, we’ll probably need to release a major update that supports the latest version of Ansible which will require deprecating formal support for those distros from this role.

@artis3n artis3n added enhancement New feature or request question Further information is requested labels Jun 17, 2024
@artis3n
Copy link
Owner Author

artis3n commented Jun 17, 2024

I think this mostly only impacts the CI suite of this repo. Anyone installing this role can continue to use this role on Ansible 9.x, as long as we don’t adopt any 10.x-specific syntax (which to my knowledge doesn’t yet exist). But If I update this repo to use Ansible 10.x, then I cannot run tests against those older distros. So staying on Ansible 9.x, for a while at least, shouldn’t have any impact on end users.

Please let me know if I’m thinking about this wrong.

Distros broken on Ansible 10:

  • Amazon Linux 2
  • AlmaLinux 8
  • Rocky Linux 8
  • RHEL 8
  • Oracle Linux 8
  • Ubuntu 18.04
  • OpenSUSE Leap (up to at least 15.6)
  • CentOS 7

@artis3n
Copy link
Owner Author

artis3n commented Jun 17, 2024

This makes me kind of want a metrics capability in the role so I can collect the distribution of OS distros targeted by this role. What % of end users would this change impact?

@McSim85
Copy link
Contributor

McSim85 commented Jun 17, 2024

Those distros looks pretty old, but some of them are still under the vendor (extended, commercial) support.
At least Ubuntu and RHEL.

https://access.redhat.com/support/policy/updates/errata#RHEL8_and_9_Life_Cycle

https://ubuntu.com/about/release-cycle

It’s a good practice to start with the “deprecation warning” message.
T
And then retire those distros, when the vendor lifecycle be retired.

Missing the CI tests sounds reasonable during the retirement period, thou

@evilhamsterman
Copy link

I would drop Ubuntu 18.04 support. It is EOL since April 2023. It has security patches with a paid support plan but I would bet the users of that at this point are very minimal. If they want/need to stick with it they are probably capable of handling themselves. I'm surprised Tailscale still advertises support for it and 16.04.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants