Automation Suite
2022.4
false
- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- 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 bundle
- 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 NIC checksum offloading
- 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
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- 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
- Cannot Log in 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 With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- 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
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- 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 Tool
- Exploring Logs
Release notes
Automation Suite Installation Guide
Last updated Apr 24, 2024
Release notes
Azure template version | 2022.4.8 |
Automation Suite version | 2022.4.2 |
Azure template version | 2022.4.7 |
Automation Suite version | 2022.4.2 |
Azure template version | 2022.4.6 |
Automation Suite version | 2022.4.1 |
Azure template version | 2022.4.5 |
Automation Suite version | 2022.4.1 |
Azure template version | 2022.4.4 |
Automation Suite version | 2022.4.0 |
- We have separated logs from operation success flags. While they both continue to be available in the storage account, they
are now stored in separate dedicated containers:
logs
andflags
, respectively. For more details, see Exploring flags and logs. - We have removed wget and unzip output to have clear logs.
- We have set a new timeout value for registration checks. The operation will fail faster when encountering network issues.
Azure template version | 2022.4.3 |
Automation Suite version | 2022.4.0 |
Azure template version | 2022.4.2 |
Automation Suite version | 2022.4.0 |
- We have introduced a series of new parameters you can use in the deployment:
Server Node Hostname
,Agent Node Hostname
,Gpu Node Hostname
, andTask Mining Node Hostname
. For parameter descriptions, see Step 2: Deploying Automation Suite to Azure.
Azure template version | 2022.4.1 |
Automation Suite version | 2022.4.0 |
- You can now perform cluster operations via Automation Account Runbooks. For details, see Azure VM lifecycle operations.
- When an Agent Virtual Machine Instance is terminated, we cordon, drain, and delete that node from the Automation Suite cluster. For details, see Instance termination.
Azure template version | 2022.4.0 |
Automation Suite version | 2022.4.0 |
- You can now install Data Service via the Azure template.
- We have added ArgoCD user password in the Key Vault.
- The Task Mining node SKU size is now exposed as a parameter.
- We have added backup configuration and resources as a nested template. You can enable or disable it via a dedicated parameter.
- We now support ultra disks, F-series VMs, and an additional GPU SKU (Standard_NC8as_T4_v3).
- We have moved SQL database creation in the ARM template, added elastic pool, and moved all databases to the elastic pool.
- Instance protection for server nodes now prevents accidental deletion that would cause data loss.
- We have segregated Virtual Machine admin credentials from the the credentials used for Automation Suite installation.
- We have added the existing SQL option when deploying the template.