- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting

Automation Suite on OpenShift installation guide
Applying a patch
An Automation Suite patch is an update to an existing version, which addresses bugs or security vulnerabilities. For instance, patch 2024.10.1+patch1 addresses issues impacting version 2024.10.1.
Instead of applying the patch, we recommend upgrading to the Cumulative Update (CU) that contains the same fix. All fixes provided in patches will also be available in the CU mentioned in the release notes for the patch.
To apply a patch to an existing Automation Suite version, take the following steps:
- Offline only. Update the registry with the latest images.
- Download the following patch artifacts from Patch artifact download links. Choose the set of artifacts applicable to your patch and registry configuration type.
- To mirror the OCI-compliant registry with the UiPath® registry, download the following artifacts:
as-images.txtas-helm-charts.txtmirror-registry.sh
- To hydrate the OCI-compliant registry with the offline bundle, download the following artifacts:
hydrate-registry.shas-cmk.tar.gz(openshift.tar.gz- starting with Automation Suite 2024.10.2)
- To mirror the OCI-compliant registry with the UiPath® registry, download the following artifacts:
- Configure the OCI-compliant registry.
Important:
Do not download the artifacts from the links referenced in the instructions on configuring the OCI-compliant registry. Instead, use the download links provided on the Patch artifact download links page.
- Download the following patch artifacts from Patch artifact download links. Choose the set of artifacts applicable to your patch and registry configuration type.
- Starting with Automation Suite 2024.10.4, download the corresponding
uipathctlpatch version from Patch artifact download links. Replace the currentuipathctlversion with the patcheduipathctlversion.Note:For details on how to set up
uipathctlCLI, refer to Running uipathctl. - Download
versions.json. For instructions, refer toPatch artifact download links. - Apply the patch by running the following commands:
-
For versions prior to Automation Suite 2024.10.4:
uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only <PRODUCTS(comma separated)>uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only <PRODUCTS(comma separated)>The following configuration sample shows how to apply a patch to Orchestrator and Action Center:
uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only orchestrator,action_centeruipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only orchestrator,action_center -
For versions starting with Automation Suite 2024.10.4:
Note:<current versions.json>refers to theversions.jsonfile for the current installation. You can find the file in the following location:<installer_directory>/versions/helm-charts.json. You must download the patchversions.jsoninto a directory, and pass the directory path to the--patch-dir-pathparameter.uipathctl cluster patch <path_to_input.json> --versions <path_to_base_versions.json> --skip-oss-prereq --only <PRODUCTS(comma separated)> --patch-dir-path <path to patch version.json files directory>uipathctl cluster patch <path_to_input.json> --versions <path_to_base_versions.json> --skip-oss-prereq --only <PRODUCTS(comma separated)> --patch-dir-path <path to patch version.json files directory>Important:For Automation Suite 2024.10.4+patch1, you must also append the
--skip-cli-compatibility-checkparameter to the patch command.The following configuration sample shows how to apply a patch to Orchestrator and Action Center:
uipathctl cluster patch <path_to_input.json> --versions <path_to_base_versions.json> --skip-oss-prereq --only orchestrator,action_center --patch-dir-path <path to patch versions.json files directory>uipathctl cluster patch <path_to_input.json> --versions <path_to_base_versions.json> --skip-oss-prereq --only orchestrator,action_center --patch-dir-path <path to patch versions.json files directory>
-
- Check if the patch operation was successful by taking the following steps:
- Run the following command to list the versions of all services:
oc -n argocd get application -o wide || helm list -Aoc -n argocd get application -o wide || helm list -A - Verify that the versions of the patched services are updated.
- Run the following command to list the versions of all services: