Automation Suite Release Notes
2023.4.1
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.
User <administrator_name> deallocated all licenses of
user(s) <user_names>
.
-
When performing a multi-node interactive installation of Automation Suite 2023.4.0, the message asking you to run the next command on secondary nodes contained an empty token. We have fixed the issue.
-
We have updated the script used for shutting down nodes to reflect the fact that it no longer supports the
--ignore-errors
flag. For details on the script, see Shutting down a node. -
We have fixed an issue causing the prerequisite check script to validate the rook-ceph raw device even when using an external objectstore.
-
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 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: Alert configurations (email and webhook receivers) get lost on reboot of machine or re-sync of
alertmanager-config
secret. For details, refer to -
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 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.
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.
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.14.1 |
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.