2022.10.10

Release date: March 11, 2024

Upgrade considerations

Upgrading to Automation Suite 2022.10.10

Before upgrading to Automation Suite 2022.10.10, keep the following guidelines in mind:

• If your current versions is 2021.10, you must upgrade to 2022.10.0-2022.10.9 first, and then to 2022.10.10.

• If your current version is 2022.4.0-2022.4.6, you must upgrade to 2022.10.0-2022.10.9 first, and then to 2022.10.10.

• If your current version is 2022.4.7, you must upgrade to 2022.10.10 or later.

  If your current version is 2022.4.11 or later, you must upgrade to 2022.10.10 or later.

For more details, see the Automation Suite upgrade paths.

Upgrading from Automation Suite 2022.10.10

If you plan to upgrade Automation Suite 2022.10.10 to 2023.10.2, it is mandatory to follow the How to upgrade from Automation Suite 2022.10.10 and 2022.4.11 to 2023.10.2 procedure.

Support for Microsoft SQL Server 2022

Erratum - Added March 25, 2024: We now support Microsoft SQL Server 2022.

New requirement for installation folder

You must now ensure that you have 20 GiB available for the opt/UiPathAutomationSuite installation folder.

New RHEL version support

We have expanded our OS support to include RHEL 8.9, alongside existing support for 8.6 and 8.8 versions.

New prerequisites validation check

For optimal cillium functionality, the prerequisites script was improved to validate that the reverse path filtering is disabled. This new check ensures that net.ipv4.conf.all.rp_filter is set to 0.

For more on the prerequisite script, see Validating the prerequisites.

Security enhancements

We continue to provide security updates and patches to address Common Vulnerabilities and Exposures (CVEs).

Bug fixes

We have modified stored procedures to handle collation differences between the SQL server and SQL database.

Known issues

OSD PV resize does not persist after upgrade

If you resize the rook-ceph OSD PV, the new size does not persist following an Automation Suite upgrade.

Redis failures due to inconsistent password updates

Erratum - added October 17, 2024: An issue is causing Redis recovery job failures when you update the ArgoCD admin password directly through the UI without simultaneously updating the Kubernetes secrets as well. To prevent the issue, we highly recommend that each time you change the ArgoCD admin password via the UI, ensure that you update the Kubernetes secrets at the same time. For more details on how to properly update the ArgoCD admin password, refer to Troubleshooting.

Pods cannot communicate with FQDN in a proxy environment

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'.

To fix the issue, see the Troubleshooting section.

Weak ciphers in TLS 1.2

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.

snapshot-controller-crds pod in CrashLoopBackOff state after upgrade

Erratum - added August 14, 2024: An issue causes the 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.

Issues related to publishing packages from Studio

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.

Issues related to persisting Alert Manager configurations during machine reboot

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 Persisting Alert Manager configurations during machine reboot.

Issue affecting the node drain function

Erratum - added April 19, 2024: An issue is causing the node-drain.sh command to fail. To prevent this situation, the node-drain.sh script must be edited to remove the --ignore-errors option for kubectl drain command.

Issues affecting Ceph metrics and alerts

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.

Issues related to CephMgrIsAbsent alerts

Erattum - added April 19, 2024: False positive CephMgrIsAbsent alerts are displayed even though there are no storage issues.

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Bundling details

Product versions

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
Automation Hub 2022.10.8	Automation Ops 2022.10.10	AI Center 2022.10.10	Action Center 2022.10.8
Task Mining 2022.10.8	AI Computer Vision 2022.10.9	Insights 2022.10.8	Apps 2022.10.7
Process Mining 2022.10.5	Document Understanding 2022.10.10	Orchestrator 2022.10.10
		Test Manager 2022.10.8
		Data Service 2022.10.10

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	11.26.11
ArgoCD	2.2.12
rook-ceph	1.8.9
cert-manager	1.9.1
rancher	2.7.6
rancher-gatekeeper	102.1.0-up3.12.0
rancher-istio	102.2.0-up1.17.2
longhorn	1.4.3
longhorn-crd	1.1.100
reloader	0.0.129
csi-driver-smb	1.10.0
rabbitmq-operator	1.5.0
redis-operator	7.2.4-7
redis-cluster	7.2.4-64
mongodb	5.0.7-ent
docker_registry	2.8.1