- 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
- Performing a 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
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Resizing Objectstore PVC
Run the following command to view more information about Objectstore.
sudo ./configureUiPathAS.sh objectstore --help
sudo ./configureUiPathAS.sh objectstore --help
Output
************************************************************************************
Manage objectstore configuration
Usage:
configureUiPathAS.sh objectstore [command]
configureUiPathAS.sh objectstore [flags]
Available Commands:
resize-pvc Resize PVC
Flags:
-h|--help Display help
************************************************************************************
************************************************************************************
Manage objectstore configuration
Usage:
configureUiPathAS.sh objectstore [command]
configureUiPathAS.sh objectstore [flags]
Available Commands:
resize-pvc Resize PVC
Flags:
-h|--help Display help
************************************************************************************
PVC resize can be dangerous and will result in downtime of entire or few of the effect components of cluster. So please, take caution before you are performing this operation.
Run the following command to view more information about resizing Objectstore PVC.
sudo ./configureUiPathAS.sh objectstore resize-pvc --help
sudo ./configureUiPathAS.sh objectstore resize-pvc --help
Output
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [mon|data]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for objectstore mon to 105 Gi
configureUiPathAS.sh objectstore resize-pvc --size 105Gi --sub-component "mon"
***************************************************************************************
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [mon|data]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for objectstore mon to 105 Gi
configureUiPathAS.sh objectstore resize-pvc --size 105Gi --sub-component "mon"
***************************************************************************************
To resize the data storage of ceph objectstore perform below command.
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1024Gi --sub-component data
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1024Gi --sub-component data
Above command will resize the data storage PVC to 1 TiB.
Before starting the PVC resize operation, tool will warn you about the impact. You must accept and only then proceed. You can also use --force flag to skip the warning.
If the attempt to resize the objstore pvc operation failed, see the Troubleshooting section for a fix.
Resizing rabbitmq PVC
To view more information about resizing rabbitmq PVC, run the following command:
sudo ./configureUiPathAS.sh rabbitmq resize-pvc --help
sudo ./configureUiPathAS.sh rabbitmq resize-pvc --help
The command returns the following output:
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [server]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for rabbitmq server to 105 Gi
configureUiPathAS.sh rabbitmq resize-pvc --size 105Gi --sub-component "server"
***************************************************************************************
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [server]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for rabbitmq server to 105 Gi
configureUiPathAS.sh rabbitmq resize-pvc --size 105Gi --sub-component "server"
***************************************************************************************
To resize the rabbitmq PVC, run the following command:
sudo ./configureUiPathAS.sh rabbitmq resize-pvc --size 100Gi --sub-component "server"
sudo ./configureUiPathAS.sh rabbitmq resize-pvc --size 100Gi --sub-component "server"
Resizing mongodb PVC
To view more information about resizing mongodb PVC, run the following command:
sudo ./configureUiPathAS.sh mongodb resize-pvc --help
sudo ./configureUiPathAS.sh mongodb resize-pvc --help
The command returns the following output:
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [data|logs]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for mongodb data to 105 Gi
configureUiPathAS.sh mongodb resize-pvc --size 105Gi --sub-component "data"
***************************************************************************************
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [data|logs]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for mongodb data to 105 Gi
configureUiPathAS.sh mongodb resize-pvc --size 105Gi --sub-component "data"
***************************************************************************************
To resize the mongodb PVC, run the following command:
sudo ./configureUiPathAS.sh mongodb resize-pvc --size 105Gi --sub-component "data"
sudo ./configureUiPathAS.sh mongodb resize-pvc --size 105Gi --sub-component "data"
The command resizes the data PVC of mongodb. If you want to resize the logs pvc, you must use --sub-component "logs".
Resizing monitoring PVC
To view more information about resizing monitoring PVC, run the following command:
sudo ./configureUiPathAS.sh monitoring resize-pvc --help
sudo ./configureUiPathAS.sh monitoring resize-pvc --help
The command returns the following output:
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [alertmanager|prometheus]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for monitoring alertmanager to 105 Gi
configureUiPathAS.sh monitoring resize-pvc --size 105Gi --sub-component "alertmanager"
***************************************************************************************
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [alertmanager|prometheus]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for monitoring alertmanager to 105 Gi
configureUiPathAS.sh monitoring resize-pvc --size 105Gi --sub-component "alertmanager"
***************************************************************************************
To resize the monitoring PVC, run the following command:
sudo ./configureUiPathAS.sh monitoring resize-pvc --size 100Gi --sub-component "alertmanager"
sudo ./configureUiPathAS.sh monitoring resize-pvc --size 100Gi --sub-component "alertmanager"
You can resize prometheus PVC by passing the value prometheus to the --sub-component argument.
Resizing registry PVC
To view more information about resizing registry PVC, run the following command:
sudo ./configureUiPathAS.sh registry resize-pvc --help
sudo ./configureUiPathAS.sh registry resize-pvc --help
The command returns the following output:
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [data]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for registry data to 105 Gi
configureUiPathAS.sh registry resize-pvc --size 105Gi --sub-component "data"
***************************************************************************************
***************************************************************************************
Resize PVC provided by different CSI drivers
Arguments
-s|--size [Required] : Size of PVC. Allowed formats are
- Plain integer
- A fixed-point number using one of these suffixes: E, P, T, G, M, k
- A fixed-point number using one of power-of-two equivalents suffixes: Ei, Pi, Ti, Gi, Mi, Ki
-b|--sub-component [Required] : Sub-component to resize. Possible Values [data]
-d|--debug Increase logging verbosity to show all debug logs
-h|--help Show this help message and exit
-f|--force Allow deletion of pods to resize the PVC. This may cause downtime
Examples
Update PVC size for registry data to 105 Gi
configureUiPathAS.sh registry resize-pvc --size 105Gi --sub-component "data"
***************************************************************************************
To resize the registry PVC, run the following command:
sudo ./configureUiPathAS.sh registry resize-pvc --size 100Gi --sub-component "data"
sudo ./configureUiPathAS.sh registry resize-pvc --size 100Gi --sub-component "data"