2023.10.6

Release date: October 17, 2024

Introducing FQDN update procedure

We are excited to announce that you can now update the Fully Qualified Domain Name (FQDN) of your Automation Suite cluster.

For details about the FQDN update procedure, see Configuring the FQDN post-installation.

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.

• We updated our documentation of the post-migration steps to clarify that you can clean up the old Redis keys for both Orchestrator and Identity from the cloud-based Redis console. For more information, see Removing old cache keys.

Corrección de errores

• Running a health check on AKS led to an [ARGOCD_REDIS_PODS] failure for ArgoCD Redis HA, although ArgoCD Redis HA is no longer used in Automation Suite on AKS. The behavior no longer occurs.
• In a proxy environment, if the proxy server used the same port as the TCP port of any other service in the Istio service mesh, such as port 8080, pods could not communicate with the FQDN, and an error message was displayed. The behavior no longer occurs.

  Note: If you previously created a service entry according to the workaround in Pods cannot communicate with FQDN in a proxy environment, we recommend that you delete the service entry after you upgrade to Automation Suite 2023.10.6 or later. To delete the service entry, use the following command:

  kubectl delete serviceentry proxy -n uipath

Problemas conocidos

Test Automation SQL connection string is ignored

Erratum - added October 17, 2024: When you provide an SQL connection string under the orchestrator.testautomation section of the input.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.

Cronología de la obsolescencia

Te recomendamos comprobar periódicamente la fecha de caducidad para ver las actualizaciones relativas a las características que quedarán obsoletas y serán eliminadas.

Detalles del paquete

Versiones de productos

Para descubrir qué ha cambiado en cada producto de Automation Suite, visita los siguientes enlaces.

Si el producto está en gris, esta nueva versión de Automation Suite no incorpora ningún cambio en él.

Discover	Crear	Administrar	Incluir
Automation Hub 2023.10.6	Automation Ops 2023.10.5	AI Center 2023.10.6	Action Center 2023.10.6
Task Mining 2023.10.6	AI Computer Vision 2023.10.6	Insights 2023.10.6	Apps 2023.10.6
Process Mining 2023.10.6	Document Understanding 2023.10.6	Orchestrator 2023.10.7
		Test Manager 2023.10.6
		Data Service 2023.10.6

Versiones de componentes internos de terceros

Para conocer las versiones de Kubernetes compatibles con cada versión de Automation Suite, consulta Compatibilidad con Kubernetes.

Esta versión de Automation Suite incluye los siguientes componentes internos:

Componente	Versión
Istio	1.23.0
ArgoCD	2.11.3
Prometheus	2.54.1
Grafana	11.1.5
Fluentd y Fluent-bit	logging-operator: 4.9.1 logging-operator-logging: 4.9.1
Gatekeeper	3.17.0
cert-manager	1.14.5
velero	6.2.0

Versión de la herramienta de migración

La versión de la herramienta de migración que necesitas depende de los productos independientes que planeas migrar y la versión de Automation Suite de destino. Para obtener más información, consulta Matriz de compatibilidad de migración.

Para obtener instrucciones sobre la migración de un producto independiente a la versión actual de Automation Suite, consulta Migración completa.