Completing the upgrade

To complete the upgrade, take the following steps:

1. Edit the cluster_config.json file to point to the cloned databases and, optionally, to the cloned buckets.
2. If you installed Automation Suite in an offline environment and upgrade from 2023.4 or earlier to 2023.10 or later, add install_type: offline to the cluster_config.json file.
3. Run the service installer on the target cluster:

   cd /opt/UiPathAutomationSuite/<version>/installer
   
   ./install-uipath.sh -i /opt/UiPathAutomationSuite/cluster_config.json -o ./output.json -s --accept-license-agreement

4. Update the certificates post-installation. For instructions, see: Managing the certificates.
5. Start the skills:
   • sync the skills:

     ./configureUiPathAS.sh aicenter skill sync [skill_ids]

   • check the skills status:

     ./configureUiPathAS.sh aicenter skill status [skill_ids]

     The command can return any of the following statuses:
     • InProgess - skill deployment is in progress.
     • Failed - skill deployment is failed.
     • OutOfSync - skill is available in the database; however, it has yet to be deployed.
     • Available - when the skills are deployed and available to consume.
6. Validate that the target cluster works as expected.

   uipathctl health check

7. Check the state of your new Automation Suite cluster related to data, connectivity, robots, and workflow.
8. Make sure the FQDN of the target cluster is the same as the FQDN of the source cluster. After updating the FQDN, switch the traffic to the new cluster.
   • Before updating FQDN, you must add the required certificates to match the FQDN.
   • To update the FQDN, see Configuring the FQDN post-installation.

   Note:

   Changing the FQDN also requires new server certificates. If a new certificate is available, you have two options: either continue with the new self-signed certificates configured by the installer automatically, or stop the installation and bring in a new certificate.

   You can configure the certificate via the server_certificate field in cluster_config.json.
9. Optionally, if you experience issues with image vulnerabilities or storage consumption, delete the images from the old installer.
10. Enable the backup on the cluster target.