2022.4.12

Release date: April 19, 2024

Support for migrating standalone Insights to Automation Suite

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.

Simplified migration to Automation Suite

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.

If, however, you have already started to manually perform this step when migrating to Automation Suite, the migration tool will ignore it and create new tenant-organization pairs. Note that the format of the automatically generated tenant name is 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.

Another significant change is the updated parameters in the UiPath.OrganizationMigrationApp tool:

• We have repurposed the following existing parameters:

  • The s parameter 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 d parameter 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 i parameter requires the Identity database connection of the standalone product.
  • The j parameter requires the Identity database connection of Automation Suite.
  • The o parameter requires the Orchestrator database connection of the standalone product.
  • The p parameter requires the URL of Automation Suite.
  • The c this parameter requires the OMS S2S client secret.

Support bundle tool improvements

We have changed the default behaviour of the support bundle tool. The default execution now generates the RKE2 bundle, in addition to the uipath, Redis, and Longhorn bundles.

We have also made the following changes to the support bundle tool arguments:

• We have deprecated the -r argument, 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 the uipath support bundle.

For more details, see Using the Automation Suite Support Bundle Tool.

Improved sf-logs cleanup process

We have improved the cleanup process for the logs stored in the 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.

Bug fixes

• Fixed an issue causing excessive alert emails after unexpected node restarts. This issue was fixed 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 occur.

Known issues

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.

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.4.10	Automation Ops 2022.4.11	AI Center 2022.4.12	Action Center 2022.4.12
Task Mining 2022.4.10	AI Computer Vision 2022.4.0	Insights 2022.4.12	Apps 2022.4.8
	Document Understanding 2022.4.12	Orchestrator 2022.4.14
		Test Manager 2022.4.11
		Data Service 2022.4.12

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.26.11
ArgoCD	2.2.5
rook-ceph	1.8.9
cert-manager	1.9.1
rancher	2.7.6
rancher-istio	102.2.0-up1.17.2
longhorn	1.4.3
longhorn-crd	1.1.100
reloader	0.0.129
csi-driver-smb	v1.10.0
rabbitmq-operator	1.5.0
redis-operator	7.2.4-7
redis-cluster	7.2.4-64
mongodb	4.4.4-ent
docker_registry	2.8.1