2022.10.14

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 Migration steps.

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

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.

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.

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 2022.10.14	Automation Ops 2022.10.13	AI Center 2022.10.14	Action Center 2022.10.12
Task Mining 2022.10.14	AI Computer Vision 2022.10.14	Insights 2022.10.12	Apps 2022.10.14
Process Mining 2022.10.14	Document Understanding 2022.10.14	Orchestrator 2022.10.14
		Test Manager 2022.10.11
		Data Service 2022.10.14

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.30.5
ArgoCD	2.11.3
rook-ceph	1.14.6
cert-manager	1.14.5
rancher	2.9.0
rancher-gatekeeper	103.1.0-up3.13.0
rancher-istio	104.4.0-up1.22.1
rancher-monitoring-crd	104.1.0-up57.0.3
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
rabbitmq-operator	2.2.0
redis-operator	7.4.6-2
redis-cluster	7.4.6-22
mongodb	5.0.7-ent
docker_registry	2.8.3

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.