- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
Automation Suite release notes
2023.10.3
Release date: April 19, 2024
We are happy to announce that you can now deploy Automation Suite in Active/Active mode. With the new configuration, you can increase system availability, boost performance by distributing workloads, and provide seamless failover by ensuring that all systems are operational and sharing the load simultaneously.
Currently, only Orchestrator supports the Active/Active setup, but we are working hard to add more products to the list.
To find out more about Active/Active configurations, see Disaster Recovery - Active/Passive and Active/Active.
The support for Active/Active deployments brings a side benefit: Automation Suite now supports external High Availability Add-on (HAA), in addition to the in-cluster configuration.
While having HAA deployed on external machines is mandatory in the case of Active/Active setups, in all the other scenarios it is optional.
For details on how to configure HAA, both when installed on the same cluster as Automation Suite and externally, see High Availability Add-on configuration and the High Availability Add-on Installation Guide.
We are excited to announce that you can now migrate your standalone Insights to Automation Suite. This migration allows you to enjoy all the benefits associated with deploying multiple UiPath on-premises products in a unified, single location. For more details, see Full migration.
Erratum - added June 3, 2024: We have made multiple improvements to the migration tool, in an attempt to streamline the process of migrating from a standalone product to Automation Suite.
One notable enhancement to highlight is the migration tool's ability to automatically create a tenant for each organization. This means that you no longer need to manually perform this operation.
tenant_xxxxxxxx, where xxxxxxxx signifies the first eight characters of the Automation Suite organization ID.
Aside from this, you no longer need to provide the tenant ID when merging the organizations.
UiPath.OrganizationMigrationApp tool:
-
We have repurposed the following existing parameters:
-
The
sparameter previously required the Identity database connection of the standalone product. Now, it requires you to provide the list of organization IDs of the standalone product. -
The
dparameter previously required the Identity database connection of Automation Suite. Now, it requires you to provide the list of organization IDs of Automation Suite.
-
-
We have introduced the following new parameters:
-
The
iparameter requires the Identity database connection of the standalone product. -
The
jparameter requires the Identity database connection of Automation Suite. -
The
oparameter requires the Orchestrator database connection of the standalone product. -
The
pparameter requires the URL of Automation Suite. -
The
cthis parameter requires the OMS S2S client secret.
-
We are striving to better support the ever evolving commercial offering of the UiPath® platform, and, as part of that, we are deprecating the option to activate licenses from the host portal. To help ease the transition, we have added a warning banner notifying administrators of the deprecation, and providing best practices for license activation.
Please rest assured that this in no way affects the functionality, and that you can still activate licenses from the host portal until the feature is removed.
uipath, Redis, and Longhorn bundles.
We have also made the following changes to the support bundle tool arguments:
-
We have deprecated the
-rargument, which used to enable the RKE2 bundle generation since the operation occurs by default now; -
We have added a new argument,
-e, to exclude the RKE2 bundle and only generate theuipathsupport bundle.
For more details, see Using the Automation Suite Support Bundle Tool.
We have added more prerequisite checks to optimize the overall experience of installing and configuring Automation Suite and to catch missing requirements earlier. Here are some highlights:
- We have introduced a new prerequisite check that validates the Redis connectivity. This check is only available if you use an external Redis cluster.
- We have added a new prerequisite check that validates that the upgrade path across Automation Suite versions is correct.
- We improved the error reporting message if the SQL prerequisite validation fails. Now, a detailed failure messages is displayed to give a better understanding of the possible issues, making it easier to troubleshoot.
For more on the prerequisite script, see Validating the prerequisites.
sf-logs bucket. A retry logic is added to the s3cmd delete command to ensure the full deletion even in case of initial failure. Additionally, the cleanup script is enhanced
to delete all logs older than the specified deletion day when the cleanup cronjob is active for a particular day.
For more on the the cleanup script, see How to clean up old logs stored in the sf-logs bundle.
infra.pod_log_path parameter in the cluster_config.json file. Previously, you could not change the /var/log/pods default log path.
/var/log/pods.
We have changed the default ArgoCD log level to Info. Previously, you had to manually change the log level.
- Erratum - added February 27, 2024: In Apps, we fixed an issue involving the filenames of files that were assigned to an app variable using a Download file from storage bucket rule, and downloaded using a File downloader control. When the pre-signed app URL was disabled, these files had erroneous file names and were missing file extensions. This behavior is now fixed.
-
Erratum - added December 15, 2024: We previously addressed an issue in an erratum dated July 3, 2024, concerning the inability to save custom configurations in the email settings due to a form validation issue. The specific issue was that the Save button appeared greyed out, even when all required fields in the form were correctly filled in. This was said to be fixed, enabling users to successfully submit the form once all necessary fields have been meticulously filled in. However, upon further review, we regret to inform you that this issue has not been completely resolved. We apologize for any confusion or inconvenience caused and want to assure you that we are actively working towards a definitive solution. Find a workaround in the known issues section.
- Erratum - added July 24, 2024: Using an external storage with a proxy environment caused Orchestrator, the Automation Suite Support Bundle Tool, Prometheus, Thanos, Fluentd, etc. to fail. The behavior no longer occurs.
-
We have fixed an issue causing the installer to miss a prerequisite check validation. The issue caused the inability to access or upgrade Orchestrator.
-
An issue was causing excessive alert emails after unexpected node restarts. We have fixed the issue by automatically managing and terminating orphaned jobs.
-
We have fixed an issue related to false positive CephMgrIsAbsent storage alerts. The alerts were displayed even though there were no storage issues. The behavior no longer occurs.
-
Ceph metrics and alerts were missing from the monitoring dashboard. The behavior no longer occurs.
-
We have fixed an issue causing a failure while uninstalling rook-ceph due to missing external object storage configuration. The error message was displayed even though the migration was succesful. The behavior no longer occurs.
-
We have fixed an issue causing the credential manager to incorrectly set the uipath-service secrets to blank.
-
We have fixed an issue preventing you from updating the TLS certificate when ArgoCD was not yet installed.
/identity_/api/setting endpoint.
Email.Smtp.UseDefaultCredentials is set to True, like in the following example:
{
"Settings": [
{
"Key": "Email.Smtp.Host",
"Value": "SendGrid"
},
{
"Key": "Email.Smtp.Port",
"Value": "587"
},
{
"Key": "Email.Smtp.UserName",
"Value": ""
},
{
"Key": "Email.Smtp.Domain",
"Value": ""
},
{
"Key": "Email.Smtp.FromEmail",
"Value": "no-reply@uipath.com"
},
{
"Key": "Email.Smtp.FromDisplayName",
"Value": "UiPath Platform"
},
{
"Key": "Email.Smtp.EnableSsl",
"Value": "true"
},
{
"Key": "Email.Smtp.UseDefaultCredentials",
"Value": "true"
},
{
"Key": "Email.Smtp.Password",
"Value": ""
},
{
"Key": "Email.Smtp.ConnectionTimeout",
"Value": "180000"
}
],
"PartitionGlobalId": ""
}{
"Settings": [
{
"Key": "Email.Smtp.Host",
"Value": "SendGrid"
},
{
"Key": "Email.Smtp.Port",
"Value": "587"
},
{
"Key": "Email.Smtp.UserName",
"Value": ""
},
{
"Key": "Email.Smtp.Domain",
"Value": ""
},
{
"Key": "Email.Smtp.FromEmail",
"Value": "no-reply@uipath.com"
},
{
"Key": "Email.Smtp.FromDisplayName",
"Value": "UiPath Platform"
},
{
"Key": "Email.Smtp.EnableSsl",
"Value": "true"
},
{
"Key": "Email.Smtp.UseDefaultCredentials",
"Value": "true"
},
{
"Key": "Email.Smtp.Password",
"Value": ""
},
{
"Key": "Email.Smtp.ConnectionTimeout",
"Value": "180000"
}
],
"PartitionGlobalId": ""
}Erratum - added December 18, 2024: An issue causes upgrades to fail when the existing Insights PVC sizes are inadvertently overridden. To address this problem, you must manually change the PVC sizes in ArgoCD UI. For details, see the Troubleshooting section.
This issue is fixed in Automation Suite 2023.10.7.
Erratum - added December 18, 2024: Following an Automation Suite upgrade from version 2023.4 or older, reinstalling or upgrading Insights results in data loss due to an issue with Insights storage class changes. To address the problem, see Troubleshooting.
We fixed the issue in Automation Suite 2023.10.7.
redis-cluster-0 pod to get stuck in the terminating state when you perform a node drain in non-HA Redis scenarios. To address the problem,
you must force delete the pod using the following command:
kubectl -n redis-system delete pod redis-cluster-0 --forcekubectl -n redis-system delete pod redis-cluster-0 --forceWe fixed the issue in Automation Suite 2023.10.7.
redis.<primary-fqdn> and redis-db.<primary-fqdn> during Active/Passive prerequisite checks. This issue is fixed in Automation Suite 2023.10.7.
Erratum - added December 18, 2024: An Insights annotation issue blocks the Automation Suite installer. We fixed the issue in Automation Suite 2023.10.7.
Erratum - added December 18, 2024: The RKE2 log collector runs indefinitely for some system commands. We fixed the issue in Automation Suite 2023.10.7.
exclude= rke2-* is not added to the /etc/yum.conf file on nodes other than the first server. In specific environments, particularly online ones, an attempt to upgrade all
components can cause an unintentional upgrade of the RKE2 service on nodes other than the first server.
exclude=rke2-* to the /etc/yum.conf file on all the nodes of your Automation Suite cluster.
aicenter skill sync and aicenter skill status commands during a side-by-side upgrade.
To fix this issue, you must manually edit the syntax. For details, see the Troubleshooting section.
orchestrator.testautomation section of the cluster_config.json file, the uipathctl binary ignores the connection string and uses the one under the orchestrator section instead. To address the problem, see the Troubleshooting section.
rook-ceph OSD PV, the new size does not persist following an Automation Suite upgrade. We fixed the issue in Automation Suite 2023.10.6.
Erratum - added October 17, 2024: When deploying Automation Suite on AWS machines where only IMDSv2 is enabled, installation fails while populating node labels. To address the issue, see the Important note in Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster.
system-upgrade namespace. If the upgrade command fails at any stage (infra, fabric, or service upgrade), take the following steps before
retrying the upgrade:
-
List the existing jobs in the
system-upgradenamespace:kubectl get jobs -n system-upgradekubectl get jobs -n system-upgrade -
Delete the failed jobs:
kubectl -n system-upgrade delete jobs <failed_jobs>kubectl -n system-upgrade delete jobs <failed_jobs>When running the command, replace the<failed_jobs>placeholder with the names of the failed jobs, separated by spaces.
We fixed the issue in Automation Suite 2023.10.6.
System.Net.Http.HttpRequestException: The proxy tunnel request to proxy 'http://<proxyFQDN>:8080/' failed with status code '404'.System.Net.Http.HttpRequestException: The proxy tunnel request to proxy 'http://<proxyFQDN>:8080/' failed with status code '404'.To fix the issue, see the Troubleshooting section.
uipathctl mistakenly processes ports in helm URLs as external registries, excluding the insecure_skip_verify: true parameter from the registries.yaml file. To overcome this issue, you must manually include the parameter in your registries.yaml file. We fixed this issue in Automation Suite 2023.10.6.
rke2-server service is shut down without executing the rke2-killall.sh script. We fixed this issue in Automation Suite 2023.10.6.
Erratum - added August 14, 2024: An issue affects the support bundle generation when using an external OCI registry in an offline environment. Under these conditions, the generated support bundle lacks historical logs and cannot upload to any selected external object storage. To fix this issue, see the Troubleshooting section.
Erratum - added August 14, 2024: Upgrading from Automation Suite 2023.10.x fails due to the Longhorn storage classes still being present. To solve the problem, you must clean up the Longhorn storage classes manually, by running the following command:
for sc in $(kubectl get sc -o json | jq -r '.items[] | select(.provisioner=="driver.longhorn.io") | .metadata.name'); do
kubectl delete sc "${sc}"
done for sc in $(kubectl get sc -o json | jq -r '.items[] | select(.provisioner=="driver.longhorn.io") | .metadata.name'); do
kubectl delete sc "${sc}"
doneWe fixed the issue in Automation Suite 2023.10.5.
ListBucket API prerequisite check fails when using an external objectstore. However, AI Center and Task Mining do not use the ListBucket API permission. We removed the unnecessary check in Automation Suite 2023.10.5.
Erratum - added August 14, 2024: You cannot enable SSO for ArgoCD due to an issue with the Dex image versions. We fixed the issue in Automation Suite 2023.10.5.
snapshot-controller-crds pod to remain in the CrashLoopBackOff state after upgrade. This occurs due to a conflict between the newly installed snapshot-controller and the existing one during the RKE2 upgrade. To fix the issue, see the Troubleshooting section.
Erratum - added August 14, 2024: In certain conditions, the Automation Suite installation process can fail due to telemetry check errors. To fix this issue, you have to manually set the telemetry check as optional and restart the installation. Starting with Automation Suite 2023.10.5, telemetry check errors no longer disrupt the installation process.
certificate-injector-webhook in deployment.apps. To address the issue, you must run the following command:
kubectl delete configmap -n uipath-infra certificate-injector-webhook-configmap --ignore-not-foundkubectl delete configmap -n uipath-infra certificate-injector-webhook-configmap --ignore-not-foundWe fixed the issue in Automation Suite 2023.10.9.
du-digitizer-worker deployment from the old Automation Suite version not being fully cleaned up after the upgrade. Starting with Automation Suite
2023.10.0, the deployment was renamed to du-digitizer-worker-deployment.
documentunderstanding application, manually delete the old du-digitizer-worker deployment. After deletion, re-sync the documentunderstanding application.
We fixed the issue in Automation Suite 2023.10.8.
Erratum - added April 15, 2025: An issue prevents the registry cleanup command from effectively clearing the unused Docker images from all registry pods. To address the issue, refer to the Troubleshooting section.
We fixed the issue in Automation Suite 2023.10.9.
Erratum - added April 15, 2025: We have identified an issue impacting the side-by-side and the in-place upgrade of Automation Suite 2022.10 or earlier to Automation Suite 2023.10.0 or later. Due to a faulty migration from MongoDB to SQL Server, the upgrade operation fails if you have Apps enabled and use Kerberos authentication for the SQL Server database.
The recommended solution is to upgrade to Automation Suite 2023.10.9.
node-monitor component, which monitors the node for issues such as checking kube-proxy health or if ip_forward is enabled, and cordons the node if issues arise, is not working for specific nodes such as GPU, task-mining, or as-robot. We have fixed this issue in Automation Suite 2023.10.9.
Erratum - added April 15, 2025: Kerberos tickets fail to automatically renew after cluster restoration, requiring manual sync of the Windows Auth app.
This issue is fixed in Automation Suite 2023.10.9.
uipathctl from correctly setting executeMigration to true during the migration process from Ceph in-cluster storage to external object storage in AI Center.
executeMigration to true in ArgoCD for AI Center and then proceed with a resync, ensuring to prune. This issue is fixed in Automation Suite 2023.10.8.
Erratum - added February 13, 2025: An issue affects the functionality of email alerts configuration and the setup of multiple receivers after upgrading from Automation Suite 2022.10. To address this issue, see Troubleshooting.
This issue is fixed in Automation Suite 2023.10.8.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
To find out what has changed on each Automation Suite product, visit the following links.
If the product is greyed out, this new Automation Suite version does not bring any changes to it.
| DISCOVER | BUILD | MANAGE | ENGAGE |
|---|---|---|---|
| AI Center 2023.10.3 | Action Center 2023.10.3 | ||
| Task Mining 2023.10.3 | AI Computer Vision 2023.10.2 | Insights 2023.10.3 | Apps 2023.10.3 |
| Document Understanding 2023.10.3 | Orchestrator 2023.10.4 | ||
| Test Manager 2023.10.3 | |||
This Automation Suite release bundles the following internal components:
|
Component |
Version |
|---|---|
|
RKE2 |
1.26.11 |
|
ArgoCD |
2.7.7 |
|
logging-operator | 4.1.0 |
| logging-operator-logging | 4.1.0 |
| gatekeeper | 3.12.0 |
|
rook-ceph |
1.9.4 |
| prometheus-pushgateway |
2.1.6 |
|
cert-manager |
1.12.3 |
|
rancher-istio |
102.2.0-up1.17.2 |
| rancher-logging | 102.0.1-up3.17.10 |
| rancher-logging-crd | 102.0.1-up3.17.10 |
| rancher-monitoring-crd | 102.0.1-up40.1.2 |
| rancher-gatekeeper-crd | 102.1.0-up3.12.0 |
| rancher-gatekeeper |
100.2.0-up3.8.1 |
| rancher-monitoring |
102.0.1-up40.1.2 |
|
longhorn |
1.4.3 |
|
longhorn-crd |
1.1.100 |
|
reloader |
0.0.129 |
|
csi-driver-smb |
1.10.0 |
|
velero |
3.1.6 |
|
redis-operator |
7.4.2-54 |
|
redis-cluster |
7.4.2-2 |
The migration tool version you need depends on the standalone products you plan to migrate and the targeted Automation Suite version. For more details, see Migration compatibility matrix.
For instructions on migrating a standalone product to the current version of Automation Suite, see Full migration.
- Support for Active/Active deployments
- Support for external High Availability Add-on
- Support for migrating standalone Insights to Automation Suite
- Simplified migration to Automation Suite
- Deprecating license activation from the host portal
- Support bundle tool improvements
- Improved prerequisite checks
- Improved sf-logs cleanup process
- Custom path for RKE2 logs
- Log-level enhancement for ArgoCD
- Bug fixes
- Known issues
- Issue with saving custom configurations in email settings
- Upgrade failure due to overridden Insights PVC sizes
- Data loss when reinstalling or upgrading Insights following Automation Suite upgrade
- Node maintenance issue in non-HA Redis
- Unnecessary Redis DNS resolution validations during Active/Passive checks
- Insights annotation issue blocks installer
- RKE2 log collector runs indefinitely
- Unintended RKE2 service upgrade on additional nodes
- AI Center skills sync failure during side-by-side upgrade
- Test Automation SQL connection string is ignored
- OSD PV resize does not persist after upgrade
- Redis failures due to inconsistent password updates
- Installation fails while populating node labels
- Cannot upgrade due to failed jobs in system-upgrade namespace
- Pods cannot communicate with FQDN in a proxy environment
- Registry configuration corruption during upgrades
- Intermittent not ready reports from agent machines
- Weak ciphers in TLS 1.2
- Support bundle log collection failure
- Upgrades fail due to Longhorn being uninstalled
- Unnecessary ListBucket API prerequisite check fails for external objectstore
- Cannot enable SSO for ArgoCD
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Installation fails due to telemetry checks
- Support bundle generated with incorrect FQDN for AKS on Azure Government
- Kubernetes upgrade failure
- Document Understanding deployment issue post-upgrade
- Incomplete Docker registry cleanup process
- Upgrade fails due to MongoDB to SQL Server migration
- Kube-proxy health check not working
- Kerberos tickets do not automatically renew
- AI Center storage migration failure
- Email alerts configuration failure post upgrade
- Deprecation timeline
- Bundling details
- Product versions
- Internal third-party component versions
- Migration tool version
