Automation Suite - Post-migration steps

automation-suite

2024.10

false

Automation Suite on Linux installation guide

Post-migration steps

Complete post-migration tasks such as removing old Identity cache keys and updating AD integration in Automation Suite.

After completing the migration, take the following steps:

To ensure a successful synchronization between Test Manager and ALM systems, follow these steps to reconfigure the Test Manager in Automation Suite:

Reconfigure the Automation Suite Test Manager URL in your ALM systems to reflect the correct location of the Test Manager.
Confirm that you can access Test Manager using the updated Automation Suite URL.
Ensure all projects and their underlying resources, including test cases, requirements, and related data, are fully restored and accessible.
Confirm that all attachments are correctly located in the external storage and can be downloaded without issues.
Reconfigure robots to point to the correct Orchestrator URL to ensure they function properly.
Update the Test Manager URL in Studio with the updated Test Manager in Automation Suite URL.

If migration fails due to another operation that is already in progress, this occurs when ArgoCD is actively processing another job or deployment for Test Manager, preventing the migration script from executing. To solve this, follow these steps:
1. Open the Arco CD UI and check the status of running processes related to Test Manager.
2. Wait until all processes are completed, and confirm that all pods are in a healthy state.
3. Re-run the the Test Manager migration script.
If the script fails to execute due to a bad interpreter, follow these steps:
1. Open a terminal in the directory where the Test Manager migration script is located.
2. Run the following command:
  dos2unix testmanager_migrator.shdos2unix testmanager_migrator.sh

To confirm that Orchestrator works correctly after the migration, take the following steps:

Check that the encryption key matches the key from UiPath.Orchestrator.dll.config by running the following command:
```
kubectl -n uipath get secret orchestrator-generated-secrets -o jsonpath='{.data.APPSETTINGS__EncryptionKey}' | base64 -d
kubectl -n uipath get secret orchestrator-generated-secrets -o jsonpath='{.data.APPSETTINGS__EncryptionKey}' | base64 -d
```
Note:
The command displays the encryption key in plain text. Handle the output as sensitive information.
Open an asset that contains a credential. If the encryption key is incorrect, Orchestrator displays an error.
Check that Orchestrator sends logs to the targets configured in NLog. If you do not store logs in the database, check that no logs are written to the database.
Download a package from the Orchestrator UI.
Upload a file to a storage bucket, and then download it.
If you use Windows Active Directory, go to the page for adding a user to a folder and check that you can search for Active Directory accounts.

On this page

PREVIOUSStep 10: Deleting the default tenant

NEXTStep 1: Removing old Identity cache keys