Troubleshooting

Pods cannot communicate with FQDN in a proxy environment

Description

Pods cannot communicate with the FQDN on a proxy environment, and the following error is displayed:

System.Net.Http.HttpRequestException: The proxy tunnel request to proxy 'http://<proxyFQDN>:8080/' failed with status code '404'.

Solution

To fix the issue, you must create a ServiceEntry, as shown in the following example:

apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
metadata:
  name: proxy
  namespace: uipath
spec:
  hosts:
  - <proxy-host>
  addresses:
  - <proxy-ip>/32
  ports:
  - number: <proxy-port>
    name: tcp
    protocol: TCP
  location: MESH_EXTERNAL

Health check of Automation Suite robots fails

Description

After installing Automation Suite on AKS, when you check the health status of the Automation Suite robots pod, it returns an unhealthy status: "[POD_UNHEALTHY] Pod asrobots-migrations-cvzfn in namespace uipath is in Failed status".

Potential issue

On rare occassions, database migrations for Orchestrator and Automation Suite robots may run at the same time. In this case, migrating the database of Automation Suite robots fails. In Argo CD, you can see two migration pods: one with a healthy status, one with an unhealthy status.

Solution

The database migration for Automation Suite robots is automatically retried, and renders successful. However, Argo CD does not update the status. You can ignore the unhealthy status.

AKS upgrades cause Automation Suite to fail

Description

An upgrade known issue affecting AKS causes Automation Suite 2023.4.1-2023.4.5 to fail. When trying to upgrade AKS, the argocd-redis-ha-server pod is put in error state.

Solution

To fix the issue, take the following steps:

1. Uninstall the existing ArgoCD chart by running the following command. Note that the kubeconfig path should be set to the cluster path.

   helm uninstall argocd -n argocd

2. Search for the profile key in the root level of input.json.
   • If it is present, change the value of the profile key to default.
   • If not present, add the "profile":"default" key in the root level ofinput.json.

3. Reinstall the ArgoCD chart by running the following command:

   uipathctl manifest apply input.json --versions versions.json --only argocd