
Automation Suite release notes
2022.10.11
Release date: April 19, 2024
We are excited to announce that you can now migrate your standalone Insights to Automation Suite. This migration allows you to enjoy all the benefits associated with deploying multiple UiPath on-premises products in a unified, single location. For more details, see Full migration.
Erratum - added June 3, 2024: We have made multiple improvements to the migration tool, in an attempt to streamline the process of migrating from a standalone product to Automation Suite.
One notable enhancement to highlight is the migration tool's ability to automatically create a tenant for each organization. This means that you no longer need to manually perform this operation.
tenant_xxxxxxxx
, where xxxxxxxx
signifies the first eight characters of the Automation Suite organization ID.
Aside from this, you no longer need to provide the tenant ID when merging the organizations.
UiPath.OrganizationMigrationApp
tool:
-
We have repurposed the following existing parameters:
-
The
s
parameter previously required the Identity database connection of the standalone product. Now, it requires you to provide the list of organization IDs of the standalone product. -
The
d
parameter previously required the Identity database connection of Automation Suite. Now, it requires you to provide the list of organization IDs of Automation Suite.
-
-
We have introduced the following new parameters:
-
The
i
parameter requires the Identity database connection of the standalone product. -
The
j
parameter requires the Identity database connection of Automation Suite. -
The
o
parameter requires the Orchestrator database connection of the standalone product. -
The
p
parameter requires the URL of Automation Suite. -
The
c
this parameter requires the OMS S2S client secret.
-
uipath
, Redis, and Longhorn bundles.
We have also made the following changes to the support bundle tool arguments:
-
We have deprecated the
-r
argument, which used to enable the RKE2 bundle generation since the operation occurs by default now; -
We have added a new argument,
-e
, to exclude the RKE2 bundle and only generate theuipath
support bundle.
For more details, see Using the Automation Suite Support Bundle Tool.
infra.pod_log_path
parameter in the cluster_config.json
file. Previously, you could not change the /var/log/pods
default log path.
/var/log/pods
.
sf-logs
bucket. A retry logic is added to the s3cmd
delete command to ensure the full deletion even in case of initial failure. Additionally, the cleanup script is enhanced
to delete all logs older than the specified deletion day when the cleanup cronjob is active for a particular day.
For more on the the cleanup script, see How to clean up old logs stored in the sf-logs bundle.
-
An issue was causing excessive alert emails after unexpected node restarts. We have fixed the issue by automatically managing and terminating orphaned jobs.
-
We have fixed an issue causing the credential manager to incorrectly set the uipath-service secrets to blank.
-
We have fixed an issue related to false positive CephMgrIsAbsent storage alerts. The alerts were displayed even though there were no storage issues. The behavior no longer occurs.
-
Ceph metrics and alerts were missing from the monitoring dashboard. The behavior no longer occur.
-
We have fixed an issue that caused
node-drain.sh
command to fail due to an outdated option.
rook-ceph
OSD PV, the new size does not persist following an Automation Suite upgrade.
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.
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.
RequestEntityTooLarge
error message. To fix the issue, see the Troubleshooting section.
alertmanager-config
secret. For details, refer to Persisting Alert Manager configurations during machine reboot.
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.
DISCOVER | BUILD | MANAGE | ENGAGE |
Automation Ops 2022.10.10 | AI Center 2022.10.11 | Action Center 2022.10.9 | |
Task Mining 2022.10.9 | AI Computer Vision 2022.10.9 | Insights 2022.10.9 | Apps 2022.10.8 |
Document Understanding 2022.10.11 | Orchestrator 2022.10.11 | ||
Test Manager 2022.10.9 | |||
This Automation Suite release bundles the following internal components:
Component |
Version |
---|---|
RKE2 |
11.26.11 |
ArgoCD |
2.2.12 |
rook-ceph |
1.8.9 |
cert-manager |
1.9.1 |
rancher |
2.7.6 |
rancher-gatekeeper | 102.1.0-up3.12.0 |
rancher-istio | 102.2.0-up1.17.2 |
longhorn |
1.4.3 |
longhorn-crd |
1.1.100 |
reloader |
0.0.129 |
csi-driver-smb |
1.10.0 |
rabbitmq-operator |
1.5.0 |
redis-operator |
7.2.4-7 |
redis-cluster |
7.2.4-64 |
mongodb |
5.0.7-ent |
docker_registry |
2.8.1 |
- Support for migrating standalone Insights to Automation Suite
- Simplified migration to Automation Suite
- Support bundle tool improvements
- Custom path for RKE2 logs
- Improved sf-logs cleanup process
- Bug fixes
- Known issues
- OSD PV resize does not persist after upgrade
- Redis failures due to inconsistent password updates
- Pods cannot communicate with FQDN in a proxy environment
- Weak ciphers in TLS 1.2
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Issues related to publishing packages from Studio
- Issues related to persisting Alert Manager configurations during machine reboot
- Deprecation timeline
- Bundling details
- Product versions
- Internal third-party component versions