automation-suite
2023.10
false
Automation Suite on EKS/AKS installation guide
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
AI Center provisioning failure after upgrading to 2023.10 or later
Cause and fix for AI Center provisioning failures after upgrading to 2023.10 or later in Automation Suite on EKS/AKS.
Description
When upgrading from 2023.4.3 to 2023.10 or later, you might run into issues when provisioning AI Center.
The system shows the following exception, and the tenant creation fails: "exception":"sun.security.pkcs11.wrapper.PKCS11Exception: CKR_KEY_SIZE_RANGE
Solution
To resolve this issue, you must perform a rollout restart of the ai-trainer deployment by running the following command:
kubectl -n uipath rollout restart deploy ai-trainer-deployment
kubectl -n uipath rollout restart deploy ai-trainer-deployment