Chapter 1. Red Hat Package Manager-based installation


If you have an existing Ansible Automation Platform 2.4 Red Hat Package Manager (RPM)-based installation of automation controller (4.4 or 4.5), you can perform a new installation of Ansible Automation Platform 2.5, which has Event-Driven Ansible controller 1.1, and configure the two installations to work together.

If you do not have an existing Ansible Automation Platform 2.4 RPM-based installation of automation controller, see the Red Hat Ansible Automation Platform installation guide, ensuring that you use an Ansible Automation Platform 2.4 installer.

Perform a new Ansible Automation Platform 2.5 RPM-based installation of Event-Driven Ansible controller 1.1 and configure it to work with an existing Ansible Automation Platform 2.4 installation of automation controller 4.4 or 4.5.

Prerequisites

  • An existing RPM-based installation of Ansible Automation Platform 2.4 with automation controller version 4.4 or 4.5.

Procedure

  1. Follow the steps provided in Installing on virtual machines until the section Installing Red Hat Ansible Automation Platform and ensure you download the Ansible Automation Platform 2.5 version of the RPM-based installer.
  2. Use the following example to populate the inventory file to deploy a new single instance of Event-Driven Ansible controller 1.1:

    # This is the Ansible Automation Platform mixed enterprise installer inventory file
    # Consult the docs if you are unsure what to add
    # For all optional variables consult the Red Hat documentation:
    # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation
    
    # This section is for your platform gateway hosts
    # -----------------------------------------------------
    [automationgateway]
    gateway1.example.org
    gateway2.example.org
    gateway3.example.org
    
    # This section is for your Event-Driven Ansible controller hosts
    # -----------------------------------------------------
    [automationedacontroller]
    eda1.example.org
    eda2.example.org
    eda3.example.org
    
    [redis]
    gateway1.example.org
    gateway2.example.org
    gateway3.example.org
    eda1.example.org
    eda2.example.org
    eda3.example.org
    
    [all:vars]
    # Common variables
    # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-general-inventory-variables
    # -----------------------------------------------------
    registry_username=<your RHN username>
    registry_password=<your RHN password>
    
    # Platform gateway
    # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-gateway-variables
    # -----------------------------------------------------
    automationgateway_admin_password=<set your own>
    automationgateway_pg_host=<set your own>
    automationgateway_pg_database=<set your own>
    automationgateway_pg_username=<set your own>
    automationgateway_pg_password=<set your own>
    
    # Event-Driven Ansible controller
    # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-controller
    # -----------------------------------------------------
    automationedacontroller_admin_password=<set your own>
    automationedacontroller_pg_host=<set your own>
    automationedacontroller_pg_database=<set your own>
    automationedacontroller_pg_username=<set your own>
    automationedacontroller_pg_password=<set your own>
    Copy to Clipboard Toggle word wrap
    Note

    Keep controller out of the inventory file. Ensure that [automationcontroller] is an empty group. Only add an Event-Driven Ansible 2.5 server. Do not add an Event-Driven Ansible 2.4 server since there is no upgrade option available

  3. Continue with the steps in Installing Red Hat Ansible Automation Platform.

1.2. Post installation steps for RPM-based install

You must complete post-install steps for setting up Ansible Automation Platform 2.5 with Event-Driven Ansible controller 1.1 and Ansible Automation Platform 2.4 with automation hub 4.9. The installation program does not handle the creation of decision environments and credentials in this scenario. See the following steps to complete the installation:

  1. Upload the 2.5 de-supported decision environment to automation hub. For more information, see Pushing a container image to private automation hub.

    Note

    If you are doing a bundle install, the image is included in the setup bundle .tar file.

  2. Create an automation hub container registry credential in Event-Driven Ansible. For more information, see Setting up credentials.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat