- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable NIC checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure After Certificate Update
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in After Migration
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Upgrading Automation Suite
Upgrading Automation Suite enables maintenance mode on the cluster, which causes downtime for the entire upgrade duration.
If your Automation Suite cluster was ever on 2021.10.3 or 2021.10.4, you must take additional steps to downgrade the Ceph objectstore version before upgrading to a newer Automation Suite version. For instructions, see Downgrading Ceph from 16.2.6 to 15.2.9.
- Make sure you meet the hardware and software requirements for new Automation Suite version.
-
Download the required installer and bundle files:
Installation type
Files to download
Online
sf-installer.zip
– Mandatory. See sf-installer.zip for download instructions.
Offline
sf-installer.zip
– Mandatory. See sf-installer.zip for download instructions.sf-infra.tar.gz
– Mandatory. See sf-infra.tar.gz for download instructions.sf.tar.gz
– Mandatory. See sf.tar.gz for download instructions.
Important:It is strongly recommended to create a backup of the cluster and the SQL database before upgrading Automation Suite. This is to ensure you can restore the cluster if something goes wrong during the upgrade operation.
Cluster data is backed up on NFS server. Make sure you have configured NFS server before proceeding further.
The following illustration shows the steps you need to take for a successful upgrade operation.
For a complete upgrade operation, follow these steps:
- Configure a backup before upgrading the cluster to a new version, if possible.
- Enable maintenance mode on the cluster, by bringing down the cluster network, to avoid any writes during upgrade. This step ensures the upgrade is consistent.
- Upgrade Kubernetes and other infrastructure components on all the cluster nodes.
- For offline installations, hydrate Private Docker Registry with the new container images.
- Upgrade the fabric and shared components on the cluster.
- Upgrade the services (UiPath products).
- Bring back the cluster by disabling the maintenance mode on the cluster.
The following matrix shows the available upgrade paths for Automation Suite versions:
- a direct in-place upgrade path between major versions is available;
- an intermediate in-place upgrade between your initial and targeted major versions is needed.
We strongly advise upgrading to the most recent minor version of Automation Suite. This allows you to take advantage of the latest enhancements and guarantees the seamless operation of all internal components.
Initial version |
Targeted version | ||||
---|---|---|---|---|---|
2021.10.x |
2022.4.x |
2022.10.x |
2023.4.x |
2023.10.x | |
2021.10.x |
|
You must upgrade to 2022.4.7-2022.4.10, and then to 2022.4.11 or later. |
You must upgrade to 2022.10.0-2022.10.9 first, and then to 2022.10.10 or later. |
You must upgrade to 2022.10.0-2022.10.9 first, and then to 2023.4.x. |
You must upgrade to 2022.10.0-2022.10.9 first, and then to 2023.10.x. |
2022.4.x |
N/A |
|
If your current version is 2022.4.0-2022.4.6, you must upgrade to 2022.10.0-2022.10.9 first, and then to 2022.10.10 or later. If your current version is 2022.4.7 or later, you must upgrade to 2022.10.10 or later. |
If your current version is 2022.4.0-2022.4.10. you must upgrade to 2022.10.0-2022.10.9 first, and then to 2023.4.x. If your current version is 2022.4.11, you must upgrade to 2022.10.10 first, and then to 2023.4.5. |
Requires 2022.4.7 minimum with Ceph on raw devices, and completion of Cilium migration before initiating the upgrade. If your current version is 2022.4.7-2022.4.10, you can upgrade to 2023.10.x. If your current version is 2022.4.11, you must upgrade to 2023.10.2 or later. |
2022.10.x |
N/A |
N/A |
|
If your current version is 2022.10.0-2022.10.9, you can upgrade to 2023.4.x. If your current version is 2022.10.10 or later, you must upgrade to 2023.4.5 or later. |
If your current version is 2022.10.0-2022.10.9, you can upgrade to 2023.10.x. If your current version is 2022.10.10 or later, you must upgrade 2023.10.2 or later. |
2023.4.x |
N/A |
N/A |
N/A |
|
If your current version is 2023.4.0-2023.4.4, you can upgrade to 2023.10.x. If your current version is 2023.4.5 or later, you must upgrade to 2023.10.2 or later. |
2023.10.x |
N/A |
N/A |
N/A |
N/A |
|
-
In some cases, upgrading Automation Suite requires transitioning through an intermediate version or skiping some versions entirely to maintain the smooth functioning of the internal components. Not following the upgrade guidelines in the previous table may lead to an internal component downgrade or an unsuccessful internal component upgrade, thereby causing the Automation Suite upgrade to fail.
-
If you plan to upgrade from Automation Suite 2022.10 or earlier, and Process Mining is enabled, you must migrate process apps to the new process graph layout before starting the upgrade.
-
If you use Active Directory (AD) and are planning on upgrading to 2023.4.0, we highly recommend that you skip straight to the 2023.4.3 version, as 2023.4.0, 2023.4.1 and 2023.4.2 are impacted by an AD issue.
-
Only upgrades to Automation Suite 2023.10 and later leverage the simplified upgrade process.