Automation Suite on Linux installation guide

Last updated Nov 6, 2025

Secret not found in UiPath namespace

Description

If service installation fails in a cluster using ceph as incluster object store, and checking kubectl -n uipath get pods returns failed pods, take the following steps.

Solution

Check kubectl -n uipath describe pod <pod-name> and look for secret not found.
If the secret is not found, then look for credential manager job logs and see if it failed.
```
# get the credential manager pod name
kubectl -n istio-system get pods | grep credential-manager
# check the credential manager pod logs
kubectl -n istio-system logs <credential-manager-pod-name># get the credential manager pod name
kubectl -n istio-system get pods | grep credential-manager
# check the credential manager pod logs
kubectl -n istio-system logs <credential-manager-pod-name>
```
If the credential manager job failed and kubectl get pods -n rook-ceph|grep rook-ceph-tool returns more than one pod, do the following:
1. delete rook-ceph-tool that is not running.
2. go to ArgoCD UI and sync sfcore appllication to retrigger the credential manager job.
3. Once the credential manager job completes, check if all secrets are created by looking at the credential-manager job logs.
4. Now sync the application corresponding to the failed pod.

On this page

Description
Solution

Was this page helpful?

PREVIOUSRKE2 server fails to start

NEXTArgoCD goes into progressing state after first installation

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy