2023.4.6

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.

New prerequisites validation check

We have added a new prerequisite check that validates that the upgrade path across Automation Suite versions is correct.

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

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.

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.

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.

Log-level enhancement for ArgoCD

We have implemented an update to ArgoCD logging. Now, the log-level is set to Info by default. Previously, you had to manually change the log-level.

Bug fixes

• Erratum - added June 23, 2025: An issue was causing the upgrade to fail when upgrading from Automation Suite 2022.10 or older to versions 2023.4.0 through 2023.4.5. This issue occurred due to an unknown socket error in the platform-services-initialize-default-organization-job, which prevented the default organization from initializing. We have fixed the issue.
• 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.

• 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 causing the credential manager to incorrectly set the uipath-service secrets to blank.

Known issues

Node maintenance issue in non-HA Redis

Erratum - added December 18, 2024: An issue causes the redis-cluster-0 pod to get stuck in the terminating state when you perform a node drain in non-HA Redis scenarios. To address the problem, you must force delete the pod using the following command:

kubectl -n redis-system delete pod redis-cluster-0 --force

We fixed the issue in Automation Suite 2023.4.10.

Insights annotation issue blocks installer

Erratum - added December 18, 2024: An Insights annotation issue blocks the Automation Suite installer. We fixed the issue in Automation Suite 2023.4.10.

RKE2 log collector runs indefinitely

Erratum - added December 18, 2024: The RKE2 log collector runs indefinitely for some system commands. We fixed the issue in Automation Suite 2023.4.10.

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.

Intermittent not ready reports from agent machines

Erratum - added October 17, 2024: An issue causes agent machines to intermittently report as not ready when the rke2-server service is shut down without executing the rke2-killall.sh script. We fixed this issue in Automation Suite 2023.4.9.

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.

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

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.

Support bundle generated with incorrect FQDN for AKS on Azure Government

Erratum - Added June 25, 2024: When generating the support bundle, an incorrect FQDN is used for AKS on Azure Government. We have fixed the issue in Automation Suite 2023.4.7.

Grafana dashboard error

Erratum - added June 10, 2025: In multi-node (HA) setups, Grafana runs with two replicas, but there is no common data source between the replicas, causing issues in user session management. Errors like Dashboard not found and Invalid dashboard UID in the request appear in the Grafana dashboard.

As a workaround, since Grafana is not a critical application, you can reduce the replica count to one by performing the following steps:

1. Modify the helm parameter for the fabric-installer application. This automatically triggers the sync operation for fabric-installer application.

   kubectl patch   application fabric-installer -n argocd    --type='json'  -p='[{"op": "add", "path": "/spec/source/helm/parameters/-", "value": {"name": "global.rancherMonitoring.grafana.replicas", "value": "1"}}]'

2. Sync the rancher-monitoring application from ArgoCD UI.

We have fixed this issue in Automation Suite 2023.4.10.

Kube-proxy health check not working

Erratum - added April 15, 2025: The node-monitor component, which monitors the node for issues such as checking kube-proxy health or if ip_forward is enabled, and cordons the node if issues arise, is not working for specific nodes such as GPU, task-mining, or as-robot. We have fixed this issue in Automation Suite 2023.4.12.

ML skill deployment failure due to token expiry

Erratum - added February 13, 2025: Due to a containerd issue, the deployment of ML skills fails as a token expires before larger image downloads can be completed, especially under conditions of slower network connectivity.

To address this isssue, see the Troubleshooting section.

Email alerts configuration failure post upgrade

Erratum - added February 13, 2025: An issue affects the functionality of email alerts configuration and the setup of multiple receivers after upgrading from Automation Suite 2022.10. To address this issue, see Troubleshooting.

This issue is fixed in Automation Suite 2023.4.11.

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.4.6	Automation Ops 2023.4.6	AI Center 2023.4.6	Action Center 2023.4.6
Task Mining 2023.4.6	AI Computer Vision 2023.4.5	Insights 2023.4.6	Apps 2023.4.6
Process Mining 2023.4.6	Document Understanding 2023.4.6	Orchestrator 2023.4.7
		Test Manager 2023.4.6
		Data Service 2023.4.6

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.26.11
ArgoCD	2.5.10
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.11.2
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.8.0
velero	3.1.6
redis-operator	7.2.4-7
redis-cluster	7.2.4-64

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.