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 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
- 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
Failure After Certificate Update
Automation Suite Installation Guide
Last updated Apr 19, 2024
Failure After Certificate Update
This issue occurs when the certificate update step fails internally. You may not able to access Automation Suite or Orchestrator.
-
Run below commands from any of the server node
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml export PATH=$PATH:/var/lib/rancher/rke2/bin kubectl -n uipath rollout restart deployments
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml export PATH=$PATH:/var/lib/rancher/rke2/bin kubectl -n uipath rollout restart deployments -
Wait for the above command to succeed and then run below command to verify the status of previous command.
deployments=$(kubectl -n uipath get deployment -o name) for i in $deployments; do kubectl -n uipath rollout status "$i" -w --timeout=600s; if [[ "$?" -ne 0 ]]; then echo "$i deployment failed in namespace uipath." fi done echo "All deployments are succeeded in namespace uipath"
deployments=$(kubectl -n uipath get deployment -o name) for i in $deployments; do kubectl -n uipath rollout status "$i" -w --timeout=600s; if [[ "$?" -ne 0 ]]; then echo "$i deployment failed in namespace uipath." fi done echo "All deployments are succeeded in namespace uipath"
Once the above command is finished execution, you should able to access Automation Suite and Orchestrator