automation-suite
2024.10
true
- Overview
- Requirements
- Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 2: Configuring the OCI-compliant registry for offline installations
- Step 3: Configuring the external objectstore
- Step 4: Configuring High Availability Add-on
- Step 5: Configuring SQL databases
- Step 6: Configuring the load balancer
- Step 7: Configuring the DNS
- Step 8: Configuring the disks
- Step 9: Configuring kernel and OS level settings
- Step 10: Configuring the node ports
- Step 11: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Cluster_config.json Sample
- General configuration
- Profile configuration
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- ArgoCD configuration
- Kerberos authentication configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- AI Center-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- 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
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating objectstore from persistent volume to raw disks
- Migrating Redis from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Scaling a single-node (evaluation) deployment to a multi-node (HA) deployment
- Monitoring and alerting
- Migration and upgrade
- 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: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Executing the upgrade
- Performing post-upgrade operations
- 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 bucket
- 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 disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to check the TLS version
- How to work with certificates
- How to schedule Ceph backup and restore data
- How to clean up unused Docker images from registry pods
- How to collect DU usage data with in-cluster objectstore (Ceph)
- How to install RKE2 SELinux on air-gapped environments
- 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
- 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
- Support bundle log collection failure
- Temporary registry installation fails on RHEL 8.9
- Frequent restart issue in uipath namespace deployments during offline installations
- DNS settings not honored by CoreDNS
- Unable to install temporary registry
- Data loss when reinstalling or upgrading Insights following Automation Suite upgrade
- Unable to access Automation Hub following upgrade to Automation Suite 2024.10.0
- Single-node upgrade fails at the fabric stage
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Volume unable to mount and remains in attach/detach loop state
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Unhealthy Insights component causes the migration to fail
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Docker registry migration stuck in PVC deletion stage
- AI Center provisioning failure after upgrading to 2023.10 or later
- Upgrade fails in offline environments
- SQL validation fails during upgrade
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Upgrade fails due to overridden Insights PVC sizes
- Failure to upgrade to Automation Suite 2024.10.1
- Upgrade fails due to Velero migration issue
- Upgrade stuck on rook-ceph application deletion
- Setting a timeout interval for the management portals
- 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
- Update the underlying directory connections
- Robot cannot connect to an Automation Suite Orchestrator instance
- Partial failure to restore backup in Automation Suite 2024.10.0
- 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
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Pods stuck in Init:0/X
- Missing Ceph-rook metrics from monitoring dashboards
- Mismatch in reported errors during diagnostic health checks
- No healthy upstream issue
- Log streaming does not work in proxy setups
- Failure to add agent nodes in offline environments
- Node becomes unresponsive (OOM) during large Document Understanding bundle upload
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- After Disaster Recovery Dapr is not working properly for Process Mining
- 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
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
- Exploring summarized telemetry
Automation Suite on Linux installation guide
Last updated Oct 17, 2025
- Q: Can I deploy Automation Suite in Active-Passive mode?
- A: Yes.
- Q: Can I deploy Automation Suite in Active-Active mode?
- A: Yes.
- Q: How many HAA licenses do I need for configuring Active/Passive?
- A: You need a total of two HAA licenses, one for each cluster. Each of the licenses must be for two shards.
- Q: Do I need to bring additional product licenses for the passive cluster?
- A: No, once you apply the licenses on the primary cluster, they are available to use in the secondary cluster as well.
- Q: Can I turn off the secondary cluster while not in use?
- A: Yes, in the case of an Active-Passive setup, you can switch off some or all nodes in the secondary cluster while not in use. In the case of an Active-Active setup, nodes on both clusters must be up and running.
- Q: Can I install unsupported products in the secondary cluster?
- A: No, you cannot install products that are not supported in the secondary cluster. If you try such an installation, the products will be unusable.
- Q: Can I rebuild the primary cluster using the secondary cluster when the backup is unavailable?
- A: No, to rebuild the primary cluster, you need a backup. However, you can rebuild the secondary cluster using the primary cluster.
- Q: Can I deploy an in-cluster objectstore with Active-Passive or Active-Active configurations?
- A: No, multi-site deployments have a strict requirement for external objectstore.
- Q: Can I perform cluster management when one of the Automation Suite clusters is unavailable or switched off?
- A: You must perform most operations, such as SQL connection string update, on both clusters. Therefore, both clusters must be available. However, if the cluster is unavailable, and you must update a configuration, you can de-link the clusters and operate individually.
- Q: If a product is down in the primary cluster, can I only switch the traffic for that product to secondary?
- A: Only site-level fault tolerance is allowed. Granular product-level tolerance is not supported right now.
- Q: Can I choose not to deploy a product in multi-site?
- A: You must install all products on both sites. You cannot choose to deploy a product only on one side except to discover products and Insights.
- Q: Can I bring heterogeneous machines in both clusters?
- A: You can bring different configurations of machines on both sites as long as those machines meet the hardware and software requirements for an Automation Suite installation.
- Q: Can I bring lower-spec machines for the secondary cluster?
- A: Yes, you can choose to deploy a smaller or fewer machines in the secondary cluster. This can be done to save some cost when Insights, Task Mining, Process Mining, and Automation Hub are not installed.
- Q: Can I run the training pipeline in the secondary cluster?
- A: You can schedule the training pipeline only on the primary cluster. This means training pipeline functionality is temporarily unavailable when the primary cluster is down.
- Q: Can I use the same Automation Suite/product license on both sites?
- A: Though both clusters are individual clusters, they are configured to behave as a single deployment. This also means you do not have to provide two separate Redis licenses.
- Q: Can I promote the secondary cluster to the primary cluster?
- A: No, you cannot promote the secondary cluster to the primary cluster.
- Q: Can I convert the multi-site deployment back to a standard Automation Suite setup?
- A: No, this is currently not possible. The only option is to recreate the setup from a backup.
- Q: What happens when the primary cluster is temporarily down in Active-Passive mode?
- A: When the primary cluster is temporarily down, Automation is temporarily unavailable. You must switch the traffic to the secondary cluster using the steps described here.
- Q: What happens when the primary cluster is temporarily down in Active-Active mode?
- A: When the primary cluster is temporarily down, products that support Active-Active mode should not experience any downtime. However, products that do not support Active-Active mode, such as Insights,Automation Hub, Process Mining, and Task Mining will be temporarily down. In this case, you should try to bring back the primary cluster.
- Q: What happens when the primary cluster is permanently down in Active-Passive mode?
- A: When the primary cluster is permanently down, Automation is temporarily unavailable. You must switch to the secondary cluster using the steps described here, then rebuild the primary cluster from backup.
- Q: What happens when the primary cluster is permanently down in Active-Active mode?
- A: When the primary cluster is permanently down, products that support Active-Active mode should not experience any downtime. However, products that do not support Active-Active mode, such as Insights,Automation Hub, Process Mining, and Task Mining will be down. You must switch the traffic to the secondary cluster, then rebuild the primary cluster from backup. After the primary cluster is up, re-enable the traffic to both clusters.
- Q: What happens when the secondary cluster is temporarily down in Active-Passive mode?
- A: When the secondary cluster is temporarily down, Automation Suite is not impacted. However, Disaster Recovery is not available. Once the secondary cluster is back, re-apply any configuration made on the primary cluster to the secondary cluster.
- Q: What happens when the secondary cluster is temporarily down in Active-Active mode?
- A: When the secondary cluster is temporarily down, Automation Suite is not impacted. However, it will not be able to serve the requests as it would have done with both the clusters up. Also, Disaster Recovery is not available. Once the secondary cluster is back, re-apply any configuration made on the primary cluster to the secondary cluster.
- Q: What happens when the secondary cluster is permanently down in Active-Passive mode?
- A: When the secondary cluster is permanently down, Automation Suite is not impacted. However, Disaster Recovery is not available. You must rebuild the secondary cluster using the primary cluster.
- Q: What happens when the secondary cluster is permanently down in Active-Active mode?
- A: When the secondary cluster is permanently down, Automation Suite is not impacted. However, it will not be able to serve the requests as it would have done with both the clusters up. Also, Disaster Recovery is not available. You must rebuild the secondary cluster using the primary cluster.
- Q: What happens when both clusters are temporarily down in Active-Passive mode?
- A: When both clusters are temporarily down, the entire Automation Suite is down until one site is online.
- Q: What happens when both clusters are temporarily down in Active-Active mode?
- A: When both clusters are temporarily down, the entire Automation Suite is down until one site is online.
- Q: What happens when both clusters are permanently down in Active-Passive mode?
- A: When both clusters are permanently down, the entire Automation Suite is down. To bring back the setup, you must restore the primary cluster using a backup, and re-build the secondary cluster from the primary cluster.
- Q: What happens when both clusters are permanently down in Active-Active mode?
- A: When both clusters are permanently down, the entire Automation Suite is down. To bring back the setup, you must restore the primary cluster using a backup, and re-build the secondary cluster from the primary cluster.
- Q: What happens when any of the products is down in the primary cluster in Active-Passive mode?
- A: When any of the products is down in the primary cluster, that product is not be available. There is no way for you to switch the traffic only for that product in the secondary cluster. And vice-versa. Only site-level fault tolerance is possible.
- Q: What happens when any of the products is down in the primary cluster in Active-Active mode?
- A: If the product that is down supports Active-Active mode then there will be no down time for that product as the secondary will be serving the requests. However, if the product does not support Active-Active mode, such as Insights,Automation Hub, Process Mining, and Task Mining, then that product will experience a downtime.
- Q: What happens when the primary data source is down, and the data is not replicated to the secondary data source in Active-Passive mode?
- A: In this case, there would be data loss. Your RPO would govern the data loss. The promotion of the secondary data source to the primary would be governed by your RTO.
- Q: What happens when the primary data source is down, and the data is not replicated to the secondary data source in Active-Active mode?
- A: In this case, there would be data loss. Your RPO would govern the data loss. The promotion of the secondary data source to the primary would be governed by your RTO.
- Q: What happens when the primary data source is back after a brief downtime in Active-Passive mode?
- A: When the primary data source is back after a brief downtime, you must ensure that unless all the data is re-synced back to the original data source, you do not start redirecting traffic to the primary cluster.
- Q: What happens when the primary data source is back after a brief downtime in Active-Active mode?
- A: When the primary data source is back after a brief downtime, you must ensure that unless all the data is re-synced back to the original data source, you do not start redirecting traffic to the primary cluster.
- Q: What happens when both data sources are down in Active-Passive mode?
- A: In this case, you should expect complete downtime. A few inflight transactions may be stuck in that state forever.
- Q: What happens when both data sources are down in Active-Active mode?
- A: In this case, you should expect complete downtime. A few inflight transactions may be stuck in that state forever.
- Q: What happens when the secondary data source is down in Active-Passive mode?
- A: In this case, Automation Suite is not impacted. You must ensure that data is replicated when the secondary data source is online.
- Q: What happens when the secondary data source is down in Active-Active mode?
- A: In this case, Automation Suite is not impacted. You must ensure that data is replicated when the secondary data source is online.
