automation-suite
2021.10
false
- 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
Unable to run an offline installation on RHEL 8.4 OS
Automation Suite Installation Guide
Last updated Aug 26, 2024
Unable to run an offline installation on RHEL 8.4 OS
The following issues can happen if you install RHEL 8.4 and are performing the offline installation, which requires podman. These issues are specific to podman and the OS being installed together. See the two below
-
you cannot install both of the following on the cluster:
podman-1.0.0-8.git921f98f.module+el8.3.0+10171+12421f43.x86_64
podman-3.0.1-6.module+el8.4.0+10607+f4da7515.x86_64
- package
cockpit-podman-29-2.module+el8.4.0+10607+f4da7515.noarch
requirespodman
>=1.3.0
, but none of the providers can be installed - cannot install the best candidate for the job
- problem with installed package
cockpit-podman-29-2.module+el8.4.0+10607+f4da7515.noarch
- package
podman-3.0.1-6.module+el8.4.0+10607+f4da7515.x86_64
requirescontainernetworking-plugins
>=0.8.1-1
, but none of the providers can be installed -
you cannot install both of the following:
containernetworking-plugins-0.7.4-4.git9ebe139.module+el8.3.0+10171+12421f43.x86_64
containernetworking-plugins-0.9.1-1.module+el8.4.0+10607+f4da7515.x86_64
- package
podman-catatonit-3.0.1-6.module+el8.4.0+10607+f4da7515.x86_64
requirespodman
=3.0.1-6.module+el8.4.0+10607+f4da7515
, but none of the providers can be installed - cannot install the best candidate for the job
-
problem with installed package
podman-catatonit-3.0.1-6.module+el8.4.0+10607+f4da7515.x86_64
(try to add--allowerasing
to command line to replace conflicting packages or--skip-broken
to skip uninstallable packages or--nobest
to use not only best candidate packages)