Automation Suite release notes

Last updated Jun 30, 2025

2023.4.9

Release date: October 17, 2024

New RHEL version supported

We have expanded our OS support to include RHEL 9.4.

New kube-proxy check

We have implemented a new kube-proxy check in the Node Monitor. If kube-proxy becomes functionally unavailable due to issues such as an iptable flush, the Node Monitor will cordon the node. Once kube-proxy functions correctly again, the node will be uncordoned.

Improved migration to Automation Suite

We made the following improvements to the migration workflows:

When moving the Identity data of your tenants from standalone Orchestrator to Automation Suite, the tenant name in Automation Suite is now the same as the original tenant name in standalone Orchestrator. Previously, the Automation Suite tenant name was automatically generated in the tenant_xxxxxxxx format, where xxxxxxxx signified the first eight characters of the Automation Suite organization ID. For more information, see Step 1: Moving the Identity organization data from standalone to Automation Suite
We updated our documentation of the migration steps to clarify that you have the option to migrate multiple standalone product tenants to either a single Automation Suite organization or multiple Automation Suite organizations. For more information, see Step 1: Moving the Identity organization data from standalone to Automation Suite and Step 4: Merging organizations in Automation Suite.

Bug fixes

We have fixed an issue where shutting down therke2-server service without executing rke2-killall.sh could lead to intermittent not ready reports from agent machines.
We have fixed an issue that caused problems during the upgrade process if you had resized the Docker-registry PVC used by your in-cluster Docker registry. Now, the new size is accurately recognized and considered during the upgrade process.
We have fixed an issue causing Redis recovery job failures when the ArgoCD admin password gets updated in the UI without also updating the Kubernetes secrets. The fix includes special handling for this scenario. We recommend to update the Kubernetes secrets at the same time when you update the ArgoCD admin password in the UI to avoid any other unexpected issues. For more details on how to properly update the ArgoCD admin password, refer to Troubleshooting.

Known issues

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:

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"}}]'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-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.

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.

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

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

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.

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.9	Automation Ops 2023.4.8	AI Center 2023.4.9	Action Center 2023.4.9
Task Mining 2023.4.9	AI Computer Vision 2023.4.9	Insights 2023.4.9	Apps 2023.4.9
Process Mining 2023.4.9	Document Understanding 2023.4.9	Orchestrator 2023.4.10
		Test Manager 2023.4.8
		Data Service 2023.4.9

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.30.5
ArgoCD	2.11.3
logging-operator	4.6.0
logging-operator-logging	4.6.0
gatekeeper	3.16.0
rook-ceph	1.14.6
prometheus-pushgateway	2.12.0
cert-manager	1.14.5
rancher-istio	104.4.0-up1.22.1
rancher-logging	103.0.0-up3.17.10
rancher-logging-crd	103.0.0-up3.17.10
rancher-monitoring-crd	104.1.0-up57.0.3
rancher-gatekeeper-crd	103.1.0-up3.13.0
rancher-gatekeeper	103.1.0-up3.13.0
rancher-monitoring	104.1.0-up57.0.3
longhorn	1.6.2
longhorn-crd	1.1.100
reloader	1.0.95
csi-driver-smb	1.16.0
velero	6.2.0
redis-operator	7.4.6-2
redis-cluster	7.4.6-22

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.

On this page