automation-suite
2023.10
false
UiPath logo, featuring letters U and I in white

Automation Suite on Linux installation guide

Last updated May 5, 2025

Performing post-upgrade operations

After completing the upgrade, you must perform the required cleanup and migration operations before starting to use the Automation Suite cluster.

The following table describes the possible scenarios where you must perform the cleanup and migration operations:

Condition

Action

  1. You upgraded from Automation Suite 2022.10 or older.

  2. Apps is installed on your Automation Suite cluster.

  1. Uninstall MongoDB by running the following command on one of the server nodes:

    ./configureUiPathAS.sh mongodb uninstall --force./configureUiPathAS.sh mongodb uninstall --force

  1. You upgraded from Automation Suite 2023.4 or older.

  2. You configured an online setup or, alternatively, an offline setup with an external registry.

  1. Add the disk for the AI Center training pipeline. For details on the requirements, see Hardware requirements for AI Center. For instructions on configuring the disk to be used for the training pipeline, see Configuring the AI Center disks on selected machines.

  2. Migrate the Longhorn volume to local volumes on the disk by running the following command:

    ./configureUiPathAS.sh longhorn migrate --excluded registry./configureUiPathAS.sh longhorn migrate --excluded registry
    Important:

    If migration fails with the "Migration failed to complete in 4500 seconds," see Troubleshooting.

    For more control and visibility, migrate each component separately. Run the help command and refer to the --included flag:
    ./configureUiPathAS.sh longhorn migrate --help./configureUiPathAS.sh longhorn migrate --help

  3. Uninstall Longhorn by running the following command:

    ./configureUiPathAS.sh longhorn uninstall./configureUiPathAS.sh longhorn uninstall
Note:

  1. You upgraded from Automation Suite 2023.4 or older.

  2. You configured an offline setup with an in-cluster registry.

  1. Add the disk for the AI Center training pipeline. For details on the requirements, see Hardware requirements for AI Center. For instructions on configuring the disk to be used for the training pipeline, see Configuring the AI Center disks on selected machines.

  2. Migrate the Longhorn volume to local volumes on the disk by running the following command:

    ./configureUiPathAS.sh longhorn migrate --config <path_to_cluster_config.json>./configureUiPathAS.sh longhorn migrate --config <path_to_cluster_config.json>

  3. Uninstall Longhorn by running the following command:

    ./configureUiPathAS.sh longhorn uninstall./configureUiPathAS.sh longhorn uninstall
Note:

  1. You upgraded to Automation Suite 2023.10.5 or newer.

  2. You configured an offline setup with an in-cluster registry.

  1. Clean up the previous version images after the upgrade from the in-cluster Docker registry. For instructions, see How to delete images from the old installer after upgrade.

  1. You configured the temporary Docker registry before the upgrade, as described in Setting up the temporary registry.

  1. Uninstall the temporary registry by running the following command:

    ./configureUiPathAS.sh registry uninstall-temp-registry -i cluster_config.json./configureUiPathAS.sh registry uninstall-temp-registry -i cluster_config.json

  1. You performed an upgrade, and you now have issues with image vulnerabilities or storage consumption.

  1. Delete the images from the old installer. For instructions, see How to delete images from the old installer after upgrade.

1. You upgrade to Automation Suite 2023.10.9 or higher.

AND

2. You enabled Process Mining.

AND

3. You have configured Airflow to use PostgreSQL as database (AutomationSuite_Airflow).

  1. Delete the Airflow Microsoft SQL Server database (AutomationSuite_Airflow).

Enabling the backup post-upgrade

Important:

Make sure Automation Suite is up and running and your automation continues as expected before proceeding with the following steps.

You must resume the backup after upgrading and performing the cleanup and migration operations. Once the cluster upgrade is done, make sure to reconfigure and upgrade Velero and then enable the backup manually.

To enable the backup, follow the instructions in described in the Backing up and restoring the cluster documentation.

Uninstalling the internal registry

Note:

This step is required if you migrated to an external OCI-compliant registry during the upgrade process.

To uninstall the internal registry, run the following command:

kubectl delete ns docker-registrykubectl delete ns docker-registry
  • Enabling the backup post-upgrade
  • Uninstalling the internal registry

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo White
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.