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
- 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
Upgrade fails due to overridden Insights PVC sizes
Description
The upgrade can fail due to an issue where existing insights PVC sizes get overridden during the process. This issue occures due to unexpected changes to the PVC sizes that are not correctly reflected during the upgrade.
Solution
To address the problem, you must manually change the PVC sizes in ArgoCD UI:
-
In the ArgoCU UI, select Insights.
-
From the upper-left corner, select the Details button and then select the Parameters tab.
-
From the upper-right corner, select the Edit button and update the
sizeparameter underinsightslooker.insightslooker.persistenceaccording to your deployed PVC size.- To retrieve the correct size of
insights-looker-lookerdir-pvc, run the following command:kubectl get pvc -n uipath insights-looker-lookerdir-pvc -o json |jq -r .status.capacity.storagekubectl get pvc -n uipath insights-looker-lookerdir-pvc -o json |jq -r .status.capacity.storage - To retrieve the correct size of
insights-looker-datadir-pvc, run the following command:kubectl get pvc -n uipath insights-looker-datadir-pvc -o json |jq -r .status.capacity.storagekubectl get pvc -n uipath insights-looker-datadir-pvc -o json |jq -r .status.capacity.storage
- To retrieve the correct size of
-
After you update the VALUES field, select the SAVE button and sync Insights.