2023.4.3
Release date: November 22, 2023
You can now migrate from a standalone UiPath® product to Automation Suite 2023.4.3 as we have released a new version of the UiPath.OrganizationMigrationApp tool. For more details, see Full migration.
Release date: November 3, 2023
We are discontinuing support for the Deployment Assistant. This will allow us to focus on further developing and refining tools that bring you greater benefits. We encourage all users to delve into our official documentation to understand the existing tools and features.
Please share your feedback on our official documentation; your input is essential in helping us continually enhance and fine-tune our offerings to best serve your needs.
Release date: October 26, 2023
All Automation Suite versions support out-of-the-box SELinux, with default policies enabled.
-
Erratum January 2024: The replica cleanup script would incorrectly reclaim storage on the nodes. For more details, see the Storage reclamation patch troubleshooting article.
-
Previously, there was an issue where well-known SIDs were inadvertently included when retrieving security groups, leading to unexpected behavior. Well-known SIDs are no longer included when fetching security groups, ensuring smoother and more predictable functionality.
-
A failure would occur when trying to rerun the Automation Suite installer 90 days after the first execution. The installer generated self-signed certificates with a 90-day validity, and rerunning it prompted the revalidation of the already expired certificates.
-
We have fixed an issue impacting the seamless operation of Orchestrator and AI Center when using an Azure Government storage account as external object store. In Orchestrator, all default packages were missing, whereas in AI Center, the deployment of Custom ML Skills failed.
-
Network policies blocked Document Understanding from configuring CORS for the internal object store. This caused single-node installations without a load balancer to fail.
-
Erratum - added October 17, 2024: In a proxy environment, if the proxy server uses the same port as the TCP port of any other service in the Istio service mesh, such as port 8080, pods cannot communicate with the FQDN. The issue causes the following error:
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.
-
Erratum - added August 29, 2024: We have identified certain vulnerabilities associated with the usage of weak ciphers in TLS 1.2. For details on how to mitigate the issue, see How to address weak ciphers in TLS 1.2.
-
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: For AI Center and Task Mining, the
ListBucket API
prerequisite check fails when using an external objectstore. However, AI Center and Task Mining do not use theListBucket API
permission. We removed the unnecessary check in Automation Suite 2023.4.8.
-
Erratum - Added June 25, 2024: When generating the support bundle, an incorrect FQDN is used for AKS on Azure Government. We have fixed the issue in Automation Suite 2023.4.7.
-
Erratum - added May 20, 2024: On single-node deployments with in-cluster storage, upgrades from version 2022.4.1 or older fail at the fabric stage due to a
rook-ceph
migration issue. To prevent the issue, follow the instructions in this troubleshooting article: Single-node upgrade fails at the fabric stage. -
Erratum - added April 19, 2024: In certain situations, Prometheus pods can fail to start due to an out-of-memory (OOM) error. To fix the issue, see the Troubleshooting section.
-
Erattum - added April 19, 2024: In certain situations, Ceph metrics and alerts are missing from the monitoring dashboards. To fix the issue, see the Troubleshooting section.
-
Erattum - added April 19, 2024: False positive CephMgrIsAbsent alerts are displayed even though there are no storage issues.
-
Erratum - added February 28, 2024: Stored procedures do not support collation differences between the SQL server and SQL database. To avoid any potential problems, you must ensure that the collation settings of both SQL server and SQL database are identical.
-
Erratum - added December 19, 2023: You cannot forward Fluentd and Fluent Bit logs to Azure and AWS government cloud storage. We recommend using Splunk and forwarding application logs there.
-
SSE-KMS
is not supported when setting up server side encryption. To fix this, change toSSE-S3
.
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.4.3 | Action Center 2023.4.3 | ||
Task Mining 2023.4.3 | AI Computer Vision 2023.4.3 | Insights 2023.4.3 | Apps 2023.4.3 |
Document Understanding 2023.4.3 | Orchestrator 2023.4.3 | ||
Test Manager 2023.4.3 | |||
This Automation Suite release bundles the following internal components:
Component |
Version |
---|---|
RKE2 |
1.24.8+rke2r1 |
ArgoCD |
2.5.10 |
logging-operator | 3.17.10 |
logging-operator-logging | 3.17.10 |
gatekeeper | 3.11.0 |
rook-ceph |
1.9.4 |
prometheus-pushgateway | 1.16.1 |
cert-manager |
1.9.1 |
rancher-istio | 100.4.0-up1.17.0 |
rancher-logging | 100.1.3-up3.17.7 |
rancher-logging-crd | 100.1.3-up3.17.7 |
rancher-monitoring-crd | 100.0.0-up16.6.0 |
rancher-gatekeeper-crd | 100.2.0-up3.8.1 |
rancher-gatekeeper | 100.2.0-up3.8.1 |
rancher-monitoring | 100.0.0-up16.6.0 |
longhorn |
1.3.3 |
longhorn-crd |
1.1.100 |
reloader |
0.0.129 |
csi-driver-smb |
1.8.0 |
velero | 2.31.3 |
redis-operator |
6.2.18-41 |
redis-cluster |
6.2.18-65 |
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.