- 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 bundle
- 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 Tool
- Exploring Logs
Downgrading Ceph From 16.2.6 to 15.2.9
Automation Suite bundles Ceph objectstore within the cluster to store files such as NuGet feeds in Orchestrator, Datasets in AI Center, and more.
Automation Suite 2021.10.3 and 2021.10.4 ship with Ceph objectstore 16.2.6. This Ceph version introduces an issue that can potentially corrupt data. As a result, Ceph has officially recalled version 16.2.6 until the issue is resolved in a newer version.
Before upgrading to a newer Automation Suite version, you must ensure the Ceph issue does not affect your cluster and the data it stores. To do that, it is required to downgrade from Ceph 16.2.6 to 15.2.9, which is a stable version.
Downgrading Ceph from 16.2.6 to 15.2.9 directly is not possible, and there are a series of operations we carry out for you when upgrading to a new Automation Suite version:
- Back up the Ceph data;
- Destroy Ceph cluster version 16.2.6;
- Recreate Ceph cluster version 15.2.9;
- Upload all the backed-up Ceph data.
To back up the Ceph data before upgrading to a new Automation Suite version, you need a temporary folder. The folder must be big enough to store all the Ceph data. To determine the size of the temporary folder required for a Ceph data backup, run the following command:
ceph_object_size=$(kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph status --format json | jq -r '.pgmap.data_bytes')
echo "You need '$(numfmt --to=iec-i $ceph_object_size)' storage space"
ceph_object_size=$(kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph status --format json | jq -r '.pgmap.data_bytes')
echo "You need '$(numfmt --to=iec-i $ceph_object_size)' storage space"
TMP_CEPH_BACKUP_PATH
variable. To create a folder and set TMP_CEPH_BACKUP_PATH
, run the following command:
# replace "/path/to/backup/ceph" with actual path where you will going to take backup mkdir -p /path/to/backup/ceph export TMP_CEPH_BACKUP_PATH="/path/to/backup/ceph"
# replace "/path/to/backup/ceph" with actual path where you will going to take backup mkdir -p /path/to/backup/ceph export TMP_CEPH_BACKUP_PATH="/path/to/backup/ceph"
/path/to/backup/ceph
with the correct Ceph path in the previous command.
For additional steps, follow the upgrade documentation.