AAP-46607: AAP-46607: Added EDA procedure when upgrading from AAP 2.4 to AAP 2.5

downstream/assemblies/platform/assembly-aap-upgrading-platform.adoc

@@ -31,6 +31,7 @@ include::platform/proc-choosing-obtaining-installer-no-internet.adoc[leveloffset
 include::platform/proc-editing-inventory-file-for-updates.adoc[leveloffset=+1]
 include::platform/con-backup-aap.adoc[leveloffset=+1]
 include::platform/proc-running-setup-script-for-updates.adoc[leveloffset=+1]
+include::platform/proc-upgrade-remove-add-eda.adoc[leveloffset=+1]
 include::platform/proc-upgrade-controller-hub-eda-unified-ui.adoc[leveloffset=+1]
 // [ddacosta] - Moved to a new post upgrade section of the doc
 //include::platform/proc-account-linking.adoc[leveloffset=+1]

downstream/modules/platform/proc-upgrade-controller-hub-eda-unified-ui.adoc

@@ -119,4 +119,4 @@ The installer upgrades {ControllerName} and {HubName} from 2.4 to {PlatformNameS
 
 * Verify that everything has upgraded to 2.5 and is working properly in one of two ways: 
 ** performing an SSH to {ControllerName} and {EDAName}.
-** In the unified UI, navigate to *Help > About* to verify the RPM versions are at 2.5.
+** In the unified UI, navigate to *Help > About* to verify the RPM versions are at 2.5.

downstream/modules/platform/proc-upgrade-remove-add-eda.adoc

@@ -0,0 +1,53 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2024-10-09
+:_mod-docs-content-type: PROCEDURE
+
+[id="upgrade-remove-and-add-eda_{context}"]
+= Removing {EDAName} 2.4 and adding {EDAName} 2.5
+
+{PlatformNameShort} {PlatformVers} supports upgrades from {PlatformNameShort} 2.4 environments for all components, except for {EDAName}. Database migrations between {EDAName} 2.4 and {EDAName} 2.5 are not compatible. Therefore, you must first upgrade the 2.4 services (using the inventory file to specify {ControllerName} and {HubName} VMs only) to get them to the initial version of {PlatformNameShort} {PlatformVers}.
+
+After all the services are at the same version, you must remove the {EDAName} 2.4 database, then add {EDAName} 2.5 and run the installer once again. After the installation is completed, reconnect {MenuAD} ({EDAcontroller}) to {MenuTopAE} ({ControllerName}) to run rulebook activations. 
+
+.Procedure
+. Shut down the old {EDAName} 2.4 host.
+. Remove the Event-Driven Ansible 2.4 database by performing the following steps:
+.. Log in to your database host with a user that has superuser privileges.
++
+`# psql -h <hostname> -U <username>`
+.. When prompted, enter your password.
+.. Delete the existing database by using the following command:
++
+`DROP DATABASE automationedacontroller`
+.. Create a new database by using the following command:
++
+`CREATE DATABASE automationedacontroller OWNER <username>`
++
+[NOTE]
+====
+If you are using a managed database, you are not required to create a new database.
+====
+.. When prompted, reenter your password.
+. Add the {EDAName} 2.5 host in the inventory file as an `[automationedacontroller]` group:
++
+----
+[automationcontroller]
+<The new Event-Driven Ansible 2.5 host>
+----
+. In the same inventory file, add the following {EDAName} variables in the inventory file under the `[all:vars]` section:
++
+----
+[all:vars]
+automationedacontroller_admin_password='<eda-password>'
+automationedacontroller_pg_host=<Your existing database host>
+automationedacontroller_pg_password='<password>'
+----
+
+. After updating the inventory file, rerun the installer using the `setup.sh` script:
++
+`$ ./setup.sh`
+. After the installation is completed, reconnect {MenuAD} ({EDAcontroller}) to {MenuTopAE} ({ControllerName}) to run rulebook activations successfully. 
+
+.Additional resources
+
+* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_decisions/eda-set-up-rhaap-credential-type[{PlatformName} credential] in the _{TitleEDAUserGuide} guide_.