Chapter 1. Red Hat Ansible Automation Platform 2.5 upgrades
1.1. Ansible Automation Platform upgrades Copy linkLink copied to clipboard!
Currently, it is possible to perform Ansible Automation Platform upgrades using one of the following supported upgrade paths.
Upgrading from Event-Driven Ansible 2.4 is not supported. If you are upgrading from Ansible Automation Platform 2.4 to 2.5 and you have deployed Event-Driven Ansible, you must first remove the Event-Driven Ansible 2.4 database and then upgrade your platform to 2.5. For information about the procedure, see Removing Event-Driven Ansible 2.4 database.
Before beginning your upgrade be sure to review the prerequisites and upgrade planning sections of this guide.
| Supported upgrade path | Steps to upgrade |
| Ansible Automation Platform 2.4 to 2.5 | Download the installation package. Set up your inventory file to match your installation environment. See Tested deployment models for a list of example inventory files. Back up your Ansible Automation Platform instance. Remove Event-Driven Ansible 2.4 database, if you deployed Event-Driven Ansible. Run the 2.5 installation program over your current Ansible Automation Platform instance. Link your existing service level accounts to a single unified platform account. |
| Ansible Automation Platform 2.5 to 2.5.x | Download the installation package. Set up your inventory file to match your installation environment. See Tested deployment models for a list of example inventory files. Back up your Ansible Automation Platform instance. Run the 2.5 installation program over your current Ansible Automation Platform instance. |
| Automation controller and automation hub 2.4 and Event-Driven Ansible 2.5 with unified UI upgrades | Upgrade the 2.4 services (using inventory file to only specify automation controller and automation hub VMs) to get them to the initial version of AAP 2.5. After all the services are at the same version, run a 2.5 upgrade on all the services |