Red Hat Ansible Tower Life Cycle

Updated -

Red Hat Ansible Tower Life Cycle

Overview

Red Hat provides a published product lifecycle for Ansible Tower so that customers and partners can properly plan, deploy, support, and maintain their enterprise automation environments.

This life cycle encompasses stated time periods for each version of Ansible Tower, such as 2.4 or 3.1. The life cycle for each version of Tower is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date. While multiple versions of Tower are supported at any one time, note that this lifecycle applies to each specific version of Tower (2.3, 2.4, 3.0, 3.1, and so on), and does not apply to a 2.x or 3.x major version as a whole.

Customers are expected to upgrade their Ansible Tower deployment to the most current supported version of the product in a timely fashion. Bug fixes and feature-work will target only the latest versions of the product, though some allowance may be given for high security risk items.

Life Cycle Dates

Ansible Tower Life Cycle

Version General Availability End of Full Support End of Maintenance Support 1 End of Maintenance Support 2 (EOL)
3.2 2017-10-02 2018-04-02 2018-10-02 2019-04-02
3.1 2017-02-28 2017-10-02 After the release of Ansible Tower 3.3 2018-10-02
3.0 2016-07-20 2017-02-28 2017-10-02 2018-02-28
2.4 2015-11-18 2016-07-20 2017-02-28 2017-07-20
2.3 2015-09-22 2015-11-18 2016-07-20 2016-11-18

Scope of Coverage

Support will be provided for use according to the published Scope of Coverage in Appendix 1 of the Red Hat Enterprise Agreement.

To encourage the rapid adoption of new technologies while keeping the high standard of stability inherent in Red Hat enterprise product, the product life cycle for Red Hat Ansible Tower is divided into three phases of maintenance, described below.

Production Phases

Full Support Phase

During the Full Support Phase, Red Hat will provide:

  • Qualified critical and important security fixes
  • Urgent and high priority bug fixes
  • Select enhanced software functionality

This will be delivered in the form of sub-minor releases.

A release of Ansible Tower is supported under the Full Support Phase for 6 months after its initial release.

Maintenance Support 1 Phase

During the Maintenance Support 1 Phase, Red Hat will provide:

  • Qualified critical security fixes
  • Urgent bug fixes

These fixes will be delivered in the form of sub-minor releases.

A release of Ansible Tower is supported under the Maintenance Support 1 Phase for 6 months after it leaves the Full Support Phase.

Maintenance Support 2 Phase

During the Maintenance Support 2 Phase, Red Hat will provide:

  • Qualified critical security fixes

These fixes will be delivered in the form of sub-minor releases.

A release of Ansible Tower is supported under the Maintenance Support 2 Phase for 6 months after it leaves the Maintenance Support 1 Phase.

All updates are provided at Red Hat’s discretion.

For information about how Red Hat works with Ansible Automation (aka Core) Support please see here

Summary:

Support Do Not Support
Installation Database Replication/Failover, Customer-Provided Database
Upgrades External applications integrated with Tower (i.e. Splunk, Okta, etc)
Backup/Restore Playbook issues without an Ansible Engine entitlement*
Configuration Custom API integrations
Usage (API and UI) Custom Inventory Scripts and Credentials
Operation Custom Ansible Tower configurations

*Unless it fails in Tower

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.