automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- 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: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
- Unable to access Automation Hub following upgrade to Automation Suite 2024.10.0
- AI Center provisioning failure after upgrading to 2023.10 or later
- Insights volumes created in two different zones following migration
- Upgrade fails due to overridden Insights PVC sizes
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Last updated Mar 31, 2026
Insights volumes created in two different zones following migration
Description
When you migrate from Automation Suite on Linux to Automation Suite on EKS/AKS and your target cluster spans multiple zones, Insights-related volumes are occasionally created in two different zones. As a result, you may encounter issues when bringing up the Insights service.
Solution
To address the problem, take the following steps:
-
Before migration, cordon the nodes in all zones, with the exception of the zone where you want the volumes to be located. To cordon the nodes, run the following command:
kubectl cordon <node name>kubectl cordon <node name> -
Execute the Automation Suite on Linux to Automation Suite on EKS/AKS migration by running the command in Step 1 of Running the cluster migration.
-
Uncordon all the nodes you cordoned before the migration by running the following command:
kubectl uncordon <node name>kubectl uncordon <node name>