- Overview
- Requirements
- Root privileges requirements
- High Availability – three availability zones
- Certificate requirements
- Network requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- 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
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- 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 TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- 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
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Support bundle log collection failure
- 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
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- 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
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Root privileges requirements
You need root privileges (sudo su) to deploy Automation Suite. The following sections describe the specific components that require root access and why they require it.
The following components require root access to configure the machines to install Automation Suite. This is required because the default partitioning structure on RHEL machines is not suitable for installing Kubernetes. All of these components are required on all nodes.
|
Component |
Why is root required to execute? |
|---|---|
|
parted |
Required to update the partition structure. |
|
pvresize |
Required to resize physical volume. |
|
lvextend |
Required to extend logical volume. |
|
xfs_growfs |
Required to expand an XFS filesystem. |
|
mkfs.ext4 |
Required to build a Linux filesystem. |
|
mount |
Required to mount a filesystem. |
The following components are required to execute the Automation Suite installer at the time of installation. All Linux components require root to be installed.
|
Component |
Node(s) the component is required for |
|---|---|
|
helm |
Server and Agent |
|
argocd |
Server |
|
jq |
Server and Agent |
|
curl |
Server and Agent |
|
openssl |
Server and Agent |
|
uuidd |
Server and Agent |
|
nc |
Server and Agent |
|
httpd-tools |
Server and Agent |
|
iscsi-initiator-utils |
Server and Agent |
|
iscsid |
Server and Agent |
|
rke2 services with Kubernetes |
Server and Agent |
|
longhorn |
Server and Agent |
|
podman1 |
Server |
1 Only required for offline installation
Of the components that were installed, the following run as root during normal Automation Suite cluster operations.
|
Component |
Node(s) the compenent is required |
Why is root required to execute? |
|---|---|---|
|
iscsi-initiator-utils |
Server and Agent |
Required to provide the server daemon for the Internet Small Computer System Interface (iSCSI) protocol, as well as the utility programs used to manage it. |
|
iscsid |
Server and Agent |
Required to implement the control path for iSCSI protocol for distributing disk access using SCSI commands sent over Internet Protocol networks, plus some management facilities. |
|
rke2 services with Kubernetes |
Server and Agent |
Required to configure containers and networking rules in the Kubernetes distribution. |
|
longhorn |
Server and Agent |
Required to manage block storage between containers and the disks on the machines. |
