- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 Disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- 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
|
Deployment mode |
Upgrade instructions |
|---|---|
|
Online single-node evaluation | |
|
Offline single-node evaluation | |
|
Online multi-node HA-ready production | |
|
Offline multi-node HA-ready production | |
|
All |
Note:
This step is optional but highly recommended when upgrading Automation Suite. |
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.
