Performing post-upgrade operations

Required cleanup and migration operations to perform after upgrading the Automation Suite cluster before resuming use.

After completing the upgrade, you must perform the required cleanup and migration operations before starting to use the Automation Suite cluster. The following scenarios describe which post-upgrade operations are required for your environment:

• If you enabled AI Center, when using an external Orchestrator, ensure you regenerate and update the installation token from Identity before attempting to sync AI Center skills. Start the skills:

  1. Sync the skills by running the following command:

     ./bin/uipathctl service aicenter sync-skills [skill_ids]
     

  2. Check the skills status by running the following command:

     ./bin/uipathctl service aicenter sync-skill-status [skill_ids]
     

     The command can return any of the following statuses:

     • InProgress - the skill deployment is in progress.
     • Failed - the skill deployment failed.
     • OutOfSync - the skill is available in the database but has not been deployed yet.
     • Available - the skills are deployed and available to consume.

  The [skill_ids] parameter is optional. For details, refer to Syncing the AI Center ML Skill.

• If you upgraded from Automation Suite 2023.4 or older and enabled AI Center, add the disk for the AI Center training pipeline. For details on the requirements, refer to Hardware requirements for AI Center. For instructions on configuring the disk, refer to Configuring the AI Center disks on selected machines.

• If you upgraded to Automation Suite 2023.10.5 or newer and configured an offline setup with an in-cluster registry, clean up the previous version images after the upgrade from the in-cluster Docker registry. For instructions, refer to How to delete images from the old installer after upgrade.

• If you are using a single-node cluster and provisioned a Ceph backup disk, manually re-enable the Ceph backup CronJob after the upgrade, as it is not automatically restored. For details, refer to How to schedule Ceph backup and restore data.

• If you configured the temporary Docker registry before the upgrade, as described in Setting up the temporary registry, uninstall the temporary registry by running the following command:

  ./bin/uipathctl registry uninstall-temp-registry -i cluster_config.json
  

• If you performed an upgrade and have issues with image vulnerabilities or storage consumption, delete the images from the old installer. For instructions, refer to How to delete images from the old installer after upgrade.

• If you upgraded to Automation Suite 2.2510.0 or higher, enabled Process Mining, and configured Airflow to use PostgreSQL as the database (AutomationSuite_Airflow), delete the Airflow Microsoft SQL Server database (AutomationSuite_Airflow).

• If you upgraded to Automation Suite 2.2510.0 or newer, you must immediately reactivate your existing licenses for each organization and host:

  • Online activation: Reactivate directly after upgrade.
  • Offline activation: Generate a new activation payload file from the Automation Suite instance, then upload it in Activation.
  • Air-gapped environments: Select 2025.10+ and download the new activation file.

  Reusing old activation files is not allowed and will result in an invalid license. License reactivation must be performed using the Update License button. Do not manually deactivate and then reactivate the license, as this action disables services.

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. To enable the backup, follow the instructions described in the Enabling the schedule snapshot backup section.

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-registry