2022.4.7
Release date: 13 June 2023
Release date: 27 June 2023
If you're considering migrating from a standalone UiPath® product to Automation Suite, we have good news for you as we have improved the process. Not only is it more straightforward, but it now covers more scenarios.
-
Migrate a standalone product to a new Automation Suite installation. This means that you do not have any products installed via Automation Suite yet, and you migrate your standalone products to a new Automation Suite instance.
-
Migrate a standalone product to a pre-existing Automation Suite installation. This means that you previously installed products via Automation Suite, and you now want to migrate more standalone products.
Erratum: 21 June 2023
We have moved the Objectstore outside the block storage and directly attached it to the nodes' disk. We have decided to implement this change so that we can reduce the replication factor for storage from 18x to 3x. While previously you needed 18 GiB of data disk to store 1 GiB of data, you now need only 3 GiB of disks. To find out more about this, check out the Hardware and software requirements and Evaluating your storage needs.
Another notable advantage of this approach is that you can scale your storage just by adding new disks without increasing the number of server nodes or changing any other configuration.
-
When Credential Manager fails due to bucket ownership being changed from one user to another, we attempt to change the ownership. Previously, we tried to create a bucket with the same name, which caused upgrade issues.
-
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.
-
Erattum - added June 25, 2024: Occasionally, some API calls from Studio or Robot can fail with a 413 error code or a
RequestEntityTooLarge
error message. To fix the issue, see the Troubleshooting section. -
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.
-
Erratum - added April 19, 2024: Alert configurations (email and webhook receivers) get lost on reboot of machine or re-sync of
alertmanager-config
secret. For details, refer to -
Erratum - 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.
-
Erratum - 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 January 2024: The replica cleanup script incorrectly reclaims storage on the nodes. For more details, see the Storage reclamation patch troubleshooting article.
-
Erratum - added November 6, 2023
In versions 2023.4.0 through 2023.4.2, if you have an Active Directory (AD) integrated environment, you will see sporadic failures from the product leading to the IIS application pool restarting. This issue has been fixed in version 2023.4.3, but it still affects the aforementioned versions. As such, if you use AD, we highly recommend that you directly install or upgrade to 2023.4.3. Otherwise, you will encounter functionality issues.
-
After restoring an Automation Suite cluster with AI Center™ enabled, you must ensure the service token and cluster credentials are pointing to the restored cluster. For more information, check the AI Center-specific section in the Troubleshooting pages.
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 2022.4.7 | Action Center 2022.4.7 | ||
Task Mining 2022.4.6 | AI Computer Vision 2022.4.0 | Insights 2022.4.7 | Apps 2022.4.4 |
Document Understanding 2022.4.7 | Orchestrator 2022.4.8 | ||
Test Manager 2022.4.6 | |||
This Automation Suite release bundles the following internal components:
Component |
Version |
---|---|
RKE2 |
v1.21.4+rke2r2 |
ArgoCD |
v2.2.5 |
rook-ceph |
v1.8.9 |
cert-manager |
1.2.0 |
rancher |
2.6.0 |
rancher-istio | 100.0.0-up1.10.4 |
longhorn |
1.3.3 |
longhorn-crd |
1.1.100 |
reloader |
v0.0.89 |
csi-driver-smb |
v1.8.0 |
rabbitmq-operator |
1.5.0 |
redis-operator |
6.2.8-11 |
redis-cluster |
6.2.8-53 |
mongodb |
4.4.4-ent |
docker_registry |
2.7.1 |
self_heal_operator |
0.0.1 |