2023.10.3

Release date: April 19, 2024

Support for Active/Active deployments

We are happy to announce that you can now deploy Automation Suite in Active/Active mode. With the new configuration, you can increase system availability, boost performance by distributing workloads, and provide seamless failover by ensuring that all systems are operational and sharing the load simultaneously.

Currently, only Orchestrator supports the Active/Active setup, but we are working hard to add more products to the list.

To find out more about Active/Active configurations, see Disaster Recovery - Active/Passive and Active/Active.

Support for external High Availability Add-on

The support for Active/Active deployments brings a side benefit: Automation Suite now supports external High Availability Add-on (HAA), in addition to the in-cluster configuration.

While having HAA deployed on external machines is mandatory in the case of Active/Active setups, in all the other scenarios it is optional.

For details on how to configure HAA, both when installed on the same cluster as Automation Suite and externally, see High Availability Add-on configuration and the High Availability Add-on Installation Guide.

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.

Deprecating license activation from the host portal

We are striving to better support the ever evolving commercial offering of the UiPath® platform, and, as part of that, we are deprecating the option to activate licenses from the host portal. To help ease the transition, we have added a warning banner notifying administrators of the deprecation, and providing best practices for license activation.

Please rest assured that this in no way affects the functionality, and that you can still activate licenses from the host portal until the feature is removed.

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 prerequisite checks

We have added more prerequisite checks to optimize the overall experience of installing and configuring Automation Suite and to catch missing requirements earlier. Here are some highlights:

• We have introduced a new prerequisite check that validates the Redis connectivity. This check is only available if you use an external Redis cluster.
• We have added a new prerequisite check that validates that the upgrade path across Automation Suite versions is correct.
• We improved the error reporting message if the SQL prerequisite validation fails. Now, a detailed failure messages is displayed to give a better understanding of the possible issues, making it easier to troubleshoot.

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

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.

Custom path for RKE2 logs

You can now opt for a custom log path for your RKE2 logs by updating the infra.pod_log_path parameter in the cluster_config.json file. Previously, you could not change the /var/log/pods default log path.

Note, however, that updating the default path discards the logs in /var/log/pods.

Log-level enhancement for ArgoCD

We have changed the default ArgoCD log level to Info. Previously, you had to manually change the log level.

Bug fixes

• Erratum - added July 24, 2024: Using an external storage with a proxy environment caused Orchestrator, the Automation Suite Support Bundle Tool, Prometheus, Thanos, Fluentd, etc. to fail. The behavior no longer occurs.

• Erratum - added July 3, 2024: When configuring the email settings, you were unable to save any custom configurations due to an issue with form validation. The Save button incorrectly appeared grayed out, despite having filled in all the required fields correctly. Now, you are able to successfully submit the form once all required fields are accurately filled in.

• We have fixed an issue causing the installer to miss a prerequisite check validation. The issue caused the inability to access or upgrade Orchestrator.

• An issue was causing excessive alert emails after unexpected node restarts. We have fixed the issue 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 occurs.

• We have fixed an issue causing a failure while uninstalling rook-ceph due to missing external object storage configuration. The error message was displayed even though the migration was succesful. The behavior no longer occurs.

• We have fixed an issue causing the credential manager to incorrectly set the uipath-service secrets to blank.

• We have fixed an issue preventing you from updating the TLS certificate when ArgoCD was not yet installed.

Known issues

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.

Support bundle log collection failure

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.

Upgrades fail due to Longhorn being uninstalled

Erratum - added August 14, 2024: Upgrading from Automation Suite 2023.10.x fails due to the Longhorn storage classes still being present. To solve the problem, you must clean up the Longhorn storage classes manually, by running the following command:

for sc in $(kubectl get sc -o json | jq -r '.items[] | select(.provisioner=="driver.longhorn.io") | .metadata.name'); do
    kubectl delete sc "${sc}"
  done

We fixed the issue in Automation Suite 2023.10.5.

Unnecessary ListBucket API prerequisite check fails for external objectstore

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 the ListBucket API permission. We removed the unnecessary check in Automation Suite 2023.10.5.

Cannot enable SSO for ArgoCD

Erratum - added August 14, 2024: You cannot enable SSO for ArgoCD due to an issue with the Dex image versions. We fixed the issue in Automation Suite 2023.10.5.

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.

Installation fails due to telemetry checks

Erratum - added August 14, 2024: In certain conditions, the Automation Suite installation process can fail due to telemetry check errors. To fix this issue, you have to manually set the telemetry check as optional and restart the installation. Starting with Automation Suite 2023.10.5, telemetry check errors no longer disrupt the installation process.

Support bundle generated with incorrect FQDN for AKS on Azure Government

When generating the support bundle, an incorrect FQDN is used for AKS on Azure Government. We fixed the issue in Automation Suite 2023.10.4.

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 2023.10.3	Automation Ops 2023.10.3	AI Center 2023.10.3	Action Center 2023.10.3
Task Mining 2023.10.3	AI Computer Vision 2023.10.2	Insights 2023.10.3	Apps 2023.10.3
Process Mining 2023.10.3	Document Understanding 2023.10.3	Orchestrator 2023.10.4
		Test Manager 2023.10.3
		Data Service 2023.10.3

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.26.11
ArgoCD	2.7.7
logging-operator	4.1.0
logging-operator-logging	4.1.0
gatekeeper	3.12.0
rook-ceph	1.9.4
prometheus-pushgateway	2.1.6
cert-manager	1.12.3
rancher-istio	102.2.0-up1.17.2
rancher-logging	102.0.1-up3.17.10
rancher-logging-crd	102.0.1-up3.17.10
rancher-monitoring-crd	102.0.1-up40.1.2
rancher-gatekeeper-crd	102.1.0-up3.12.0
rancher-gatekeeper	100.2.0-up3.8.1
rancher-monitoring	102.0.1-up40.1.2
longhorn	1.4.3
longhorn-crd	1.1.100
reloader	0.0.129
csi-driver-smb	1.10.0
velero	3.1.6
redis-operator	7.4.2-54
redis-cluster	7.4.2-2

Migration tool version

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.