Chapter 2. Upgrading to Red Hat Ansible Automation Platform 2.5

Upgrades to Ansible Automation Platform 2.5 include the platform gateway. Ensure you review the 2.5 Network ports and protocols for architectural changes and Tested deployment models for information on opinionated deployment models.

You have reviewed the centralized Redis instance offered by Ansible Automation Platform for both standalone and clustered topologies.

Prior to upgrading your Red Hat Ansible Automation Platform, ensure you have reviewed Planning your installation for a successful upgrade. You can then download the desired version of the Ansible Automation Platform installer, configure the inventory file in the installation bundle to reflect your environment, and then run the installer.

Before you begin the upgrade process, review the following considerations to plan and prepare your Ansible Automation Platform deployment:

Choose the Red Hat Ansible Automation Platform installer you need based on your Red Hat Enterprise Linux environment internet connectivity. Review the following scenarios and decide on which Red Hat Ansible Automation Platform installer meets your needs.

Before upgrading your Red Hat Ansible Automation Platform installation, edit the inventory file so that it matches your desired configuration. You can keep the same parameters from your existing Ansible Automation Platform deployment or you can modify the parameters to match any changes to your environment.

You can find sample inventory files in the Test topologies GitHub repository, or in our Tested deployment models guide.

Back up an existing Ansible Automation Platform instance by running the .setup.sh script with the backup_dir flag, which saves the content and configuration of your current environment.

With a successful backup, a backup file is created at /ansible/mybackup/automation-platform-backup-<date/time>.tar.gz .

You can run the setup script once you have finished updating the inventory file.

The installation will begin.

Ansible Automation Platform 2.5 supports upgrades from Ansible Automation Platform 2.4 environments for all components, with the exception of Event-Driven Ansible. You can also configure a mixed environment with Event-Driven Ansible from 2.5 connected to a legacy 2.4 cluster. Combining install methods (OCP, RPM, Containerized) within such a topology is not supported by Ansible Automation Platform.

Supported topologies described in this document assume that:

[automationcontroller]
controller-1
controller-2

[automationhub]
hub-1
hub-2

[all:vars]
# Here we have the admin passwd, db credentials, etc.

[edacontroller]
eda-1
eda-2

[gateway]
gw-1
gw-2

[all:vars]
# Here we have admin passwd, db credentials etc.

[automationcontroller]
controller-1
controller-2

[automationhub]
hub-1
hub-2

[edacontroller]
eda-1
eda-2

[gateway]
gw-1
gw-2

[all:vars]
# Here we have admin passwd, db credentials etc from both inventories above

Ansible Automation Platform 2.5 provides a centralized location for users, teams and organizations to access the platform’s services and features. When you upgrade from a previous version of Ansible Automation Platform, your existing account is automatically migrated to a single platform account. However, if you have multiple component accounts, your accounts must be linked to use the centralized features of the platform.

The first time you log in to Ansible Automation Platform 2.5, the platform searches through the existing services to locate a user account with the credentials you entered. When there is a match to an existing account, that account is registered and becomes centrally managed by the platform. Any subsequent component accounts in the system are orphaned and cannot be used to log into the platform.

To address this problem, use the account linking procedure to authenticate from any of your existing component accounts and still be recognized by the platform. Linking accounts associates existing component accounts with the same user profile.

You can also link your legacy account manually by taking the following steps:

If you encounter an error message telling your that your account could not be authenticated, contact your platform administrator.

After you have migrated your user account, you can manage your account from the Access Management menu. See Managing access with role based access control.