- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
Automation Suite release notes
2023.10.1
Release date: December 19, 2023
Red Hat no longer supports RHEL 8.3, 8.4, 8.5, and 8.7. As a result, we have removed them from the list of compatible RHEL versions. We currently support RHEL 8.6 and 8.8, but we recommend using the latter.
If you move from an older Automation Suite version, make sure you use a supported RHEL version before starting the upgrade.
For more details, see the Automation Suite hardware and software requirements.
--bundle-type flag when running the hydrate-registry.sh script when configuring your OCI-compliant registry.
- Erratum - Added June 25, 2024: We have fixed a logging configuration issue that was causing the host machine storage to fill up due to Redis logs accumulating
in
/var/lib/rancher. -
Erratum - added May 20, 2024: Previously, on single-node deployments with in-cluster storage, upgrades from version 2022.4.1 or older would fail at the fabric stage. A
rook-cephmigration issue was causing the failure. The behavior no longer occurs. -
Previously, when installing the required RPM packages, if the
cluster_config.jsonfile was missing, an error was thrown. Now, if the file does not exist when running./validateUiPathASReadiness.sh install-packages, we assume that you perform an online installation, and no error prompts you. -
We have fixed an issue causing trigger zombie processes to start after performing a 2023.10.0 offline installation.
Erratum - added December 18, 2024: An issue causes upgrades to fail when the existing Insights PVC sizes are inadvertently overridden. To address this problem, you must manually change the PVC sizes in ArgoCD UI. For details, see the Troubleshooting section.
This issue is fixed in Automation Suite 2023.10.7.
Erratum - added December 18, 2024: Following an Automation Suite upgrade from version 2023.4 or older, reinstalling or upgrading Insights results in data loss due to an issue with Insights storage class changes. To address the problem, see Troubleshooting.
We fixed the issue in Automation Suite 2023.10.7.
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 --forcekubectl -n redis-system delete pod redis-cluster-0 --forceWe fixed the issue in Automation Suite 2023.10.7.
redis.<primary-fqdn> and redis-db.<primary-fqdn> during Active/Passive prerequisite checks. This issue is fixed in Automation Suite 2023.10.7.
Erratum - added December 18, 2024: An Insights annotation issue blocks the Automation Suite installer. We fixed the issue in Automation Suite 2023.10.7.
exclude= rke2-* is not added to the /etc/yum.conf file on nodes other than the first server. In specific environments, particularly online ones, an attempt to upgrade all
components can cause an unintentional upgrade of the RKE2 service on nodes other than the first server.
exclude=rke2-* to the /etc/yum.conf file on all the nodes of your Automation Suite cluster.
aicenter skill sync and aicenter skill status commands during a side-by-side upgrade.
To fix this issue, you must manually edit the syntax. For details, see the Troubleshooting section.
orchestrator.testautomation section of the cluster_config.json file, the uipathctl binary ignores the connection string and uses the one under the orchestrator section instead. To address the problem, see the Troubleshooting section.
Erratum - added October 17, 2024: When deploying Automation Suite on AWS machines where only IMDSv2 is enabled, installation fails while populating node labels. To address the issue, see the Important note in Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster.
system-upgrade namespace. If the upgrade command fails at any stage (infra, fabric, or service upgrade), take the following steps before
retrying the upgrade:
-
List the existing jobs in the
system-upgradenamespace:kubectl get jobs -n system-upgradekubectl get jobs -n system-upgrade -
Delete the failed jobs:
kubectl -n system-upgrade delete jobs <failed_jobs>kubectl -n system-upgrade delete jobs <failed_jobs>When running the command, replace the<failed_jobs>placeholder with the names of the failed jobs, separated by spaces.
We fixed the issue in Automation Suite 2023.10.6.
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 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: 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 for sc in $(kubectl get sc -o json | jq -r '.items[] | select(.provisioner=="driver.longhorn.io") | .metadata.name'); do
kubectl delete sc "${sc}"
doneWe fixed the issue in Automation Suite 2023.10.5.
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.
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 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.
Erratum - added August, 2024: Migrating from an in-cluster objectstore to an external objectstore fails due to a configuration issue. Therefore, you must not attempt a migration from the Ceph in-cluster objectstore to an external objectstore in this version of Automation Suite. We fixed the issue in Automation Suite 2023.10.2, where you can safely migrate from Ceph to an external objectstore.
Erratum - added July 24, 2024: Using an external storage with a proxy environment causes Orchestrator, the Automation Suite Support Bundle Tool, Prometheus, Thanos, Fluentd, etc. to fail. We fixed the issue in Automation Suite 2023.10.3.
/identity_/api/setting endpoint.
Email.Smtp.UseDefaultCredentials is set to True, like in the following example:
{
"Settings": [
{
"Key": "Email.Smtp.Host",
"Value": "SendGrid"
},
{
"Key": "Email.Smtp.Port",
"Value": "587"
},
{
"Key": "Email.Smtp.UserName",
"Value": ""
},
{
"Key": "Email.Smtp.Domain",
"Value": ""
},
{
"Key": "Email.Smtp.FromEmail",
"Value": "[email protected]"
},
{
"Key": "Email.Smtp.FromDisplayName",
"Value": "UiPath Platform"
},
{
"Key": "Email.Smtp.EnableSsl",
"Value": "true"
},
{
"Key": "Email.Smtp.UseDefaultCredentials",
"Value": "true"
},
{
"Key": "Email.Smtp.Password",
"Value": ""
},
{
"Key": "Email.Smtp.ConnectionTimeout",
"Value": "180000"
}
],
"PartitionGlobalId": ""
}{
"Settings": [
{
"Key": "Email.Smtp.Host",
"Value": "SendGrid"
},
{
"Key": "Email.Smtp.Port",
"Value": "587"
},
{
"Key": "Email.Smtp.UserName",
"Value": ""
},
{
"Key": "Email.Smtp.Domain",
"Value": ""
},
{
"Key": "Email.Smtp.FromEmail",
"Value": "[email protected]"
},
{
"Key": "Email.Smtp.FromDisplayName",
"Value": "UiPath Platform"
},
{
"Key": "Email.Smtp.EnableSsl",
"Value": "true"
},
{
"Key": "Email.Smtp.UseDefaultCredentials",
"Value": "true"
},
{
"Key": "Email.Smtp.Password",
"Value": ""
},
{
"Key": "Email.Smtp.ConnectionTimeout",
"Value": "180000"
}
],
"PartitionGlobalId": ""
}Erratum - added June 3, 2024: Ocassionally the network policies for Airflow prevent the DNS from working correctly. To prevent the issue, run the following command.
sudo networkPolicyTool.sh --createNetworkPolicy ./Configs/networkPolicyTool/airflow.yaml --addsudo networkPolicyTool.sh --createNetworkPolicy ./Configs/networkPolicyTool/airflow.yaml --addErattum - added April 19, 2024: False positive CephMgrIsAbsent alerts are displayed even though there are no storage issues. This issue is fixed in Automation Suite 23.10.3.
Erratum - added April 19, 2024: When uninstalling rook-ceph, an error message related to missing external object storage configuration is displayed. This issue occurs even though the migration is succesful. This behavior is fixed in Automation Suite 23.10.3.
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.
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 February 28, 2024: We have identified an issue impacting the side-by-side and the in-place upgrade of Automation Suite 2022.10 or earlier to Automation Suite 2023.10.0 or later. Due to a faulty migration from MongoDB to SQL Server, the upgrade operation fails if you have Apps enabled and use Kerberos authentication for the SQL Server database.
Erratum - added April 15, 2025: The recommended solution is to upgrade to Automation Suite 2023.10.9.
Erratum - added February 28, 2024: Whenever trying to add a new product to an existing Automation Suite installation, the installer wrongly asks you to provide a temporary registry, causing a failure in the installation process.
To solve the problem, use the following workaround:
- Make sure the temporary registry is up.
- Change the readinessProbe setting of the docker registry StatefulSet by running the following command:
kubectl patch statefulset docker-registry -n docker-registry --type json -p '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"httpGet":{"scheme":"HTTPS", "path": "/", "port": 5000}}}]'kubectl patch statefulset docker-registry -n docker-registry --type json -p '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"httpGet":{"scheme":"HTTPS", "path": "/", "port": 5000}}}]'
Erratum - added June 26, 2025: An issue causes the addition process of agent nodes in offline environments to fail. Agent node additions require the temporary registry to be running. To address the issue, you must re-enable the temporary registry to successfully join the agent node.
We fixed the issue in Automation Suite 2023.10.10.
CertificatePolicies section with policy OID values exceeding 4 bytes. This issue prevents Automation Suite from recognizing these CA certificates,
interrupting the installation process.
CertificatePolicies section do not exceed 4 bytes, or avoid using CA generators that add the CertificatePolicies section to the certificates.
We fixed the issue in Automation Suite 2023.10.10.
Erratum - added June 26, 2025: Licensing SQL connection errors occur when the Data Source property specified both a named instance and a port.
We fixed the issue in Automation Suite 2023.10.10.
Dashboard not found and
Invalid dashboard UID in the request appear in the Grafana
dashboard.
-
Modify the helm parameter for the
fabric-installerapplication. This automatically triggers the sync operation forfabric-installerapplication.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"}}]'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"}}]' - Sync the
rancher-monitoringapplication from ArgoCD UI.
We have fixed this issue in Automation Suite 2023.10.7.
Erratum - added May 21, 2025: For offline Automation Suite installations using the external docker registry, the uipathctl health check command does not work due to a known issue. This issue has been fixed in Automation Suite 2023.10.6.
As a workaround, you can download the uipathctl binary from Automation Suite 2023.10.6 and use it to run the uipathctl health check command.
certificate-injector-webhook in deployment.apps. To address the issue, you must run the following command:
kubectl delete configmap -n uipath-infra certificate-injector-webhook-configmap --ignore-not-foundkubectl delete configmap -n uipath-infra certificate-injector-webhook-configmap --ignore-not-foundWe fixed the issue in Automation Suite 2023.10.9.
du-digitizer-worker deployment from the old Automation Suite version not being fully cleaned up after the upgrade. Starting with Automation Suite
2023.10.0, the deployment was renamed to du-digitizer-worker-deployment.
documentunderstanding application, manually delete the old du-digitizer-worker deployment. After deletion, re-sync the documentunderstanding application.
We fixed the issue in Automation Suite 2023.10.8.
Erratum - added April 15, 2025: An issue prevents the registry cleanup command from effectively clearing the unused Docker images from all registry pods. To address the issue, refer to the Troubleshooting section.
We fixed the issue in Automation Suite 2023.10.9.
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.10.9.
Erratum - added April 15, 2025: Kerberos tickets fail to automatically renew after cluster restoration, requiring manual sync of the Windows Auth app.
This issue is fixed in Automation Suite 2023.10.9.
uipathctl from correctly setting executeMigration to true during the migration process from Ceph in-cluster storage to external object storage in AI Center.
executeMigration to true in ArgoCD for AI Center and then proceed with a resync, ensuring to prune. This issue is fixed in Automation Suite 2023.10.8.
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.10.8.
platform-services-initialize-default-organization-job, which prevents the default organization from initializing.
We fixed the issue in Automation Suite 2023.10.3.
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.26.5 |
|
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.8.0 |
|
velero |
3.1.6 |
|
redis-operator |
7.2.4-7 |
|
redis-cluster |
7.2.4-64 |
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.
- Out-of-support RHEL versions
- Registry hydration improvements
- Bug fixes
- Known issues
- Upgrade failure due to overridden Insights PVC sizes
- Data loss when reinstalling or upgrading Insights following Automation Suite upgrade
- Node maintenance issue in non-HA Redis
- Unnecessary Redis DNS resolution validations during Active/Passive checks
- Insights annotation issue blocks installer
- Unintended RKE2 service upgrade on additional nodes
- AI Center skills sync failure during side-by-side upgrade
- Test Automation SQL connection string is ignored
- Installation fails while populating node labels
- Cannot upgrade due to failed jobs in system-upgrade namespace
- Pods cannot communicate with FQDN in a proxy environment
- Weak ciphers in TLS 1.2
- Support bundle log collection failure
- Upgrades fail due to Longhorn being uninstalled
- Unnecessary ListBucket API prerequisite check fails for external objectstore
- Cannot enable SSO for ArgoCD
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Migration from in-cluster objectstore to external objectstore fails
- Components fail when using external object storage with proxy environment
- Issue with saving custom configurations in email settings
- Network policies in Airflow may cause improper functioning of DNS
- Issues related to CephMgrIsAbsent alerts
- Error message while uninstalling rook-ceph post migrating to a S3 object-store
- Issues affecting Ceph metrics and alerts
- Collation differences between SQL server and SQL database not supported
- Upgrade fails due to MongoDB to SQL Server migration
- Installation failure when adding new products to existing Automation Suite
- Agent node addition failure in offline environments
- Installation fails due to CA certificates with large policy OIDs
- Licensing SQL connection error
- Grafana dashboard error
- uipathctl health check command
- Kubernetes upgrade failure
- Document Understanding deployment issue post-upgrade
- Incomplete Docker registry cleanup process
- Kube-proxy health check not working
- Kerberos tickets do not automatically renew
- AI Center storage migration failure
- Email alerts configuration failure post upgrade
- Upgrade failure due to default organization initialization
- Deprecation timeline
- Bundling details
- Product versions
- Internal third-party component versions
- Migration tool version
