Chapter 2. Upgrading to Red Hat Ansible Automation Platform 2.4

• Even if you have a valid license from a previous version, you must provide your credentials or a subscriptions manifest upon upgrading to the latest version of automation controller.
• If you need to upgrade Red Hat Enterprise Linux and automation controller, you must first backup and restore your automation controller data.
• Clustered upgrades require special attention to instance and instance groups before upgrading.

• When upgrading to Ansible Automation Platform 2.4, you can either add an existing automation hub API token or generate a new one and invalidate any existing tokens.
• Existing container images are removed when upgrading Ansible Automation Platform. This is because, when upgrading Ansible Automation Platform with setup.sh script, podman system reset -f is executed. This removes all container images on your Ansible Automation Platform nodes then pushes the new execution environment image that is bundled with installer. See Running the Red Hat Ansible Automation Platform installer setup script.

• If you are currently running Event-Driven Ansible controller and plan to deploy it when you upgrade to Ansible Automation Platform 2.4, it is recommended that you disable all Event-Driven Ansible activations before upgrading to ensure that only new activations run after the upgrade process has completed. This prevents possibilities of orphaned containers running activations from the previous version.

Provisioning new nodes in a cluster

• Add new nodes alongside existing nodes in the inventory file as follows:

  [controller]
  clusternode1.example.com
  clusternode2.example.com
  clusternode3.example.com
  
  [all:vars]
  admin_password='password'
  
  pg_host=''
  pg_port=''
  
  pg_database='<database_name>'
  pg_username='<your_username>'
  pg_password='<your_password>'

Deprovisioning nodes or groups in a cluster

• Append node_state-deprovision to the node or group within the inventory file.

• Import an existing API token with the automationhub_api_token flag as follows:

  automationhub_api_token=<api_token>

• Generate a new API token, and invalidate any existing tokens, with the generate_automationhub_token flag as follows:

  generate_automationhub_token=True