automation-suite
2022.10
false
- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Downloading the installation packages
- Install-uipath.sh Parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating objectstore from persistent volume to raw disks
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Configuring the FQDN post-installation
- Setting up Kerberos authentication
- Setting up Elasticsearch and Kibana
- Saving robot logs to Elasticsearch
- Forwarding application logs to Splunk
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Automation Suite Installation Guide
Last updated Nov 21, 2024
Configuring the FQDN post-installation
To update the FQDN of Automation Suite, you need to run the installer again and make the following changes in the
cluster_config.json file for all the nodes in the cluster.
fqdn- update this field with new FQDN that you need to access the cluster.Important:Thefqdnfield only supports lowercase letters.
fixed_rke_address- if this value is identical to thefqdnfield incluster_config.json, then you need to update this value as well to reflect the new FQDN.Note:Changing the FQDN also requires new server certificates. If a new certificate is available, you have two options: either continue with the new self-signed certificate configured by the installer automatically, or stop the installation and bring in a new certificate.
You can configure the certificate via theserver_certificatefield incluster_config.json.
To update the FQDN in single-node evaluation mode, take the following steps:
- Navigate to the
UiPathAutomationSuitefolder (the location of the installer bundle). - Run the following command to update the FQDN:
Online
sudo ./install-uipath.sh -i ./cluster_config.json -o output.json -a --accept-license-agreementsudo ./install-uipath.sh -i ./cluster_config.json -o output.json -a --accept-license-agreement
Offline
Run the following command to update the FQDN for the infrastructure:
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreementsudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreementRun the following command to update the FQDN for the fabric and services:
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --install-type offline --accept-license-agreementsudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --install-type offline --accept-license-agreementNote: The installer warns you of the consequences of updating the FQDN. It asks for confirmation before proceeding further. The
installer also warns you if there is no new valid certificate related to the FQDN.
To update the FQDN in multi-node HA-ready production mode, take the following steps:
Run the installer on all the machines (server and agent nodes). Note that the order of execution is very important. You first
need to run the installer on all the servers, and then on all remaining agent nodes as well as the Task Mining node.
Note:
There are some variations between the commands you run on the first server node, those you execute on the subsequent server nodes, and those you use on agent nodes, as follows:
- The
-aoption is exclusively for commands executed on the first server node. This is where you must run the fabric and service installer. - The
-koption specifically applies to commands run on the following server nodes, and it skips the execution of the fabric and service installer. - The
-j serveroption is used to distinguish between server nodes and agent nodes.
