- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- How to disable TX 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Automation Suite installation guide
Root privileges requirements
You need root privileges (sudo su) to deploy Automation Suite. The following sections describe the specific components that require root access and why they require it.
The following components require root access to configure the machines to install Automation Suite. This is required because the default partitioning structure on RHEL machines is not suitable for installing Kubernetes. All of these components are required on all nodes.
|
Component |
Why is root required to execute? |
|---|---|
|
parted |
Required to update the partition structure. |
|
pvresize |
Required to resize physical volume. |
|
lvextend |
Required to extend logical volume. |
|
xfs_growfs |
Required to expand an XFS filesystem. |
|
mkfs.ext4 |
Required to build a Linux filesystem. |
|
mount |
Required to mount a filesystem. |
The following components are required to execute the Automation Suite installer at the time of installation. All Linux components require root to be installed.
|
Component |
Node(s) the component is required for |
|---|---|
|
helm |
Server and Agent |
|
argocd |
Server |
|
jq |
Server and Agent |
|
curl |
Server and Agent |
|
openssl |
Server and Agent |
|
uuidd |
Server and Agent |
|
nc |
Server and Agent |
|
httpd-tools |
Server and Agent |
|
iscsi-initiator-utils |
Server and Agent |
|
iscsid |
Server and Agent |
|
rke2 services with Kubernetes |
Server and Agent |
|
longhorn |
Server and Agent |
|
podman1 |
Server |
1 Only required for offline installation
Of the components that were installed, the following run as root during normal Automation Suite cluster operations.
|
Component |
Node(s) the component is required for |
Why is root required to execute? |
|---|---|---|
|
iscsi-initiator-utils |
Server and Agent |
Required to provide the server daemon for the Internet Small Computer System Interface (iSCSI) protocol, as well as the utility programs used to manage it. |
|
iscsid |
Server and Agent |
Required to implement the control path for iSCSI protocol for distributing disk access using SCSI commands sent over Internet Protocol networks, plus some management facilities. |
|
rke2 services with Kubernetes |
Server and Agent |
Required to configure containers and networking rules in the Kubernetes distribution. |
|
longhorn |
Server and Agent |
Required to manage block storage between containers and the disks on the machines. |
