Red Hat Ansible Automation Platform is ending support for Ansible Core 2.15 and Python 3.11

oranod
Fri, 20 Mar 2026 16:48:25 +0000
Red Hat partners

To ensure the continued stability, security, and performance of Red Hat Ansible Automation Platform (AAP), Red Hat is updating our certification requirements for partner collections.

What is changing?

Red Hat Ansible Automation Platform is ending support for Ansible Core 2.15 and Python 3.11.

As a result, compatibility with Ansible Core 2.16 as the minimum required version will be a mandatory prerequisite for collection certification or validation. Likewise certified and validated collections must be tested against Python 3.12 to ensure compatibility with AAP.

This transition is driven by critical technical and lifecycle milestones, as follows:

Following the lifecycle for AAP 2.4, support for Ansible Core 2.15 is reaching End of Life for Critical Security Fixes. For reference, see Table 1.1 - Current AAP and Ansible Core lifecycles on the Red Hat Ansible Automation Platform Life Cycle page.

AAP is rebuilding on Python 3.12 to facilitate upgrades from Django 4 to Django 5.2 LTS and come into tighter alignment with the RHEL Python lifecycle.

When do these changes occur?

These new compatibility requirements for certified and validated collections come into effect on Monday, May 18, 2026.

These lifecycle changes are coming into effect sooner than the May deadline. We encourage all partners to upgrade collection compatibility with Ansible Core 2.16 and Python 3.12 as soon as convenient.

However we also recognize that it can take time to adjust to changes and update collection testing. With this in mind, the Partner engineering team at Red Hat will continue certifying collections that require Ansible Core 2.15 during the period of transition.

The Partner engineering team at Red Hat is also available to assist with collection test coverage against Python 3.12 in that same timeframe.

Red Hat customers will continue to have access to execution environments (EEs) that work against Python 3.11 and Ansible Core 2.15. However the health status of those EEs will slowly degrade while they also reach the end of support.

Next Steps

We recommend that you begin testing your collections against Ansible Core 2.16 and Python 3.12 as soon as possible to identify any necessary code adjustments or dependency updates.

1. Audit your collection’s meta/runtime.yml file and update requires_ansible: to >=2.16.0.

2. Update your CI/CD testing matrix to include Python 3.12.

Run ansible-test sanity against Ansible Core 2.16 and Python 3.12.

1 post - 1 participant

Read full topic