- Overview
- Requirements
- Recommended: Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 1: Configuring the OCI-compliant registry for offline installations
- Step 2: Configuring the external objectstore
- Step 3: Configuring High Availability Add-on
- Step 4: Configuring Microsoft SQL Server
- Step 5: Configuring the load balancer
- Step 6: Configuring the DNS
- Step 7: Configuring kernel and OS level settings
- Step 8: Configuring the disks
- Step 9: Configuring the node ports
- Step 10: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Step 13: Generating cluster_config.json
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL 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
- 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
- install-uipath.sh parameters
- 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 from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- 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
- Redirecting traffic for the unsupported services to the primary cluster
- Monitoring and alerting
- Migration and upgrade
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- 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
- Migrating to an external OCI-compliant registry
- 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 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 disable NIC checksum offloading
- How to upgrade from Automation Suite 2022.10.10 and 2022.4.11 to 2023.10.2
- How to manually set the ArgoCD log level to Info
- 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
- Cluster unhealthy after automated upgrade from 2021.10
- 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
- Upgrade fails in offline environments
- 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
- 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
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Missing Ceph-rook metrics from monitoring dashboards
- Running the diagnostics tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Step 4: Merging organizations in Automation Suite
\
before special characters.
To merge organizations in Automation Suite, run the following command:
./UiPath.OrganizationMigrationApp merge -i '<identity database connection of Automation Suite>' -o '<restored orchestrator DB in Automation Suite connection string>' -s '<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>' -d '<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>'
./UiPath.OrganizationMigrationApp merge -i '<identity database connection of Automation Suite>' -o '<restored orchestrator DB in Automation Suite connection string>' -s '<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>' -d '<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>'
-
Make sure to add
TrustServerCertificate=True
for both the source and destination SQL connections in the input. -
If you have multiple organization pairs to merge, make sure the organization ID sequence for the standalone product and the organization ID sequence for Automation Suite match.
To merge organizations in Automation Suite, run the following command:
./UiPath.OrganizationMigrationApp merge -i "<identity database connection of Automation Suite>" -o "<restored orchestrator DB in Automation Suite connection string>" -s "<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>" -d "<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>"
./UiPath.OrganizationMigrationApp merge -i "<identity database connection of Automation Suite>" -o "<restored orchestrator DB in Automation Suite connection string>" -s "<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>" -d "<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>"
TrustServerCertificate=True
for both source and destination SQL connection strings in the input.
When running the UiPath.OrganizationMigrationApp tool, you must provide the following details:
-
The list of organization IDs for the standalone product
-
The list of organization IDs for Automation Suite
Make sure to use the same organization IDs as the ones identified in Step 1: Moving the Identity organization data from standalone to Automation Suite.
Condition |
Does the source user has an email address? |
Does the target user has an email address? |
Is the source user email the same as the one of the target user? |
Is the source username the same as the target username? |
Result |
1 |
|
|
|
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
2 |
|
|
|
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. After the merge, two users have the same username, and they must use the email address to login. |
3 |
|
|
|
or |
The source user is merged with the target user; the target user has access to standalone Orchestrator. |
4 |
|
|
N/A |
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
5 |
|
|
N/A |
|
The source user is merged with the target user; the target user has access to standalone Orchestrator. |
6 |
|
|
N/A |
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
7 |
|
|
N/A |
|
You must manually configure the email address for the target user or remove the target user. If you configure the email address, the source user is merged with the target user, and the target user has access to standalone Orchestrator. If you remove the target user, the source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
8 |
|
|
N/A |
|
The source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
9 |
|
|
N/A |
|
You must configure the email address to be empty for the target user or remove the target user. If you configure the email address as empty, the source user is merged with the target user, and the target user has access to standalone Orchestrator. If you remove the target user, the source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
If the source and target robot usernames are the same, the source robot user is appended the user ID and is move to the target organization.
Source robot username |
Target robot username |
Moved source robot username |
sameRobot |
sameRobot |
|
If the source and target robot group names are the same, the source robot user is appended a string and is moved to the target organization.
Source group name |
Target group name |
Moved source group username |
sameGroup |
sameGroup |
|
If the organization merge failed, check the logs. Depending on whether the Identity or the Orchestrator migration failed, take the following steps:
If the Identity migration failed, you can just fix the error and execute the organization merge command again. This would rollback all the changes since we have set a transaction for operations for Identity.
If the Orchestrator migration failed, the Orchestrator database would roll back, but the Identity database would not rollback. As a result, you must restore the backup of the Identity database and replace the connection string to use the new database. After fixing the error, run organization merge command again.
If the Orchestrator migration failed, take the following steps:
-
Restore the backup of the Identity database.
-
Right-click the database directory and select Import Data-tier Application.
-
Select the backup database file.
-
Input the backup database name.
-
Wait for the process to complete.
-
-
Replace the identity connection string.
`"platform": { "sql_connection_str": "<dotnet connection string>", (added line) "enabled": true, },`
`"platform": { "sql_connection_str": "<dotnet connection string>", (added line) "enabled": true, },` -
Fix the error and use the new platform connection string to run the merge command again.