2023.4.5

Release date: February 28, 2024

Upgrade considerations

Automation Suite 2023.4.5 and 2023.10.2 include an upgrade to Kubernetes 1.26.11. As such, when upgrading Automation Suite, you must ensure you do not downgrade Kubernetes. To do that, when moving from Automation Suite 2023.4.5 or a later minor version to the next major version, you must upgrade to 2023.10.2 at a minimum.

Support for Microsoft SQL Server 2022

Erratum - Added March 25, 2024: We now support Microsoft SQL Server 2022.

New prerequisites validation check

Erratum - Added March 11, 2024: For optimal Cillium functionality, we have improved the prerequisites script to validate that the reverse path filtering is disabled. This new check ensures that net.ipv4.conf.all.rp_filter is set to 0.

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

New RHEL version support

We have expanded our OS support to include RHEL 8.9, alongside existing support for 8.6 and 8.8 versions.

Security enhancements

We continue to provide security updates and patches to address Common Vulnerabilities and Exposures (CVEs).

Bug fixes

We have modified stored procedures to handle collation differences between the SQL server and SQL database.

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.

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.

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.

Issues related to CephMgrIsAbsent alerts

Erattum - added April 19, 2024: False positive CephMgrIsAbsent alerts are displayed even though there are no storage issues.

Issues affecting Ceph metrics and alerts

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.

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.

Upgrade failure due to default organization initialization

Erratum - added June 23, 2025: An issue causes the upgrade to fail when upgrading from Automation Suite 2022.10 or older to versions 2023.4.0 through 2023.4.5. The issue occurs due to an unknown socket error in the platform-services-initialize-default-organization-job, which prevents the default organization from initializing.

We fixed the issue in Automation Suite 2023.4.6.

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

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.