Automation Suite
2022.10
false
- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Downloading the installation packages
- Install-uipath.sh Parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- 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
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- 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
- Authentication not working 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 due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- 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
- ArgoCD goes into progressing state after first installation
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- 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
Automation Suite Installation Guide
Last updated Apr 24, 2024
Release Notes
| AWS template version | 2022.10.5 |
| Automation Suite version | 2022.10.5 |
| AWS template version | 2022.10.5 |
| Automation Suite version | 2022.10.5 |
| AWS template version | 2022.10.4 |
| Automation Suite version | 2022.10.2 |
| AWS template version | 2022.10.3 |
| Automation Suite version | 2022.10.1 |
The AWS deployment template now provides support for upgrades to newer Automation Suite versions.
After performing an Automation Suite upgrade, the Azure template deployment requires some adjustments to ensure that new nodes
join the cluster correctly. To automate these changes, we recommend using the
upgrade_wrapper.py script. For more details and instructions, see Completing an upgrade.
| AWS template version | 2022.10.3 |
| Automation Suite version | 2022.10.1 |
| AWS template version: | 2022.10.2 |
| Automation Suite version | 2022.10.0 |
| AWS template version | 2022.10.1 |
| Automation Suite version | 2022.10.0 |
| AWS template version | 2022.10.0 |
| Automation Suite version | 2022.10.0 |
- You can now install new services using the AWS deployment template. Process Mining and Automation Suite Robots are the latest additions to the suite.
- You can now connect AI Center to an external Orchestrator. To do that, you must explicitly opt for this functionality and provide certificates for Orchestrator and Identity. For more instructions, see Step 1: Preparing the AWS deployment.
- You can now install strictly the products you are interested in using the AWS deployment template as we have deprecated the Basic product selection and made Orchestrator optional.
- We have introduced a new tool guiding you through the steps you need to take to complete the Automation Suite installation as well as common post-installation operations. It is called Cluster Administration, and it provides useful instructions on certificate configuration, Kerberos authentication setup, node administration, database maintenance, cluster monitoring, and more.
- The AWS template now defaults to using RHEL 8.6.
- We have some new Systems Manager documents for connecting AI Center to an external Orchestrator and for backup and restore operations. For more details, see Performing cluster operations.
-
The hardware requirements for Automation Suite have been optimized. As a result, we have also made some changes to the AWS deployment architecture to reflect these improvements. For details, see Complete component list.
For details on how the template computes the required hardware, see Deployment and instance type mapping.
-
Following the deprecation of the the Basic product selection for Automation Suite, we now have two options to launch the AWS CloudFormation template:
- into a new VPC
- into an existing VPC
- We have made some changes to EC2 instance configuration for the server nodes. The disk configuration now includes an Objectstore disk, used for in-cluster storage.
- This release also brings various UX improvements.
Erratum: We have fixed the issue in AWS template version 2022.10.4, which installs Automation Suite 2022.10.2. For more details, see 27 February 2023 release notes.
- While Automation Suite now provides support for external storage, the AWS deployment template currently does not offer this functionality. For the time being, you need to continue using the in-cluster storage, but we are actively working on providing an alternative.
