ArgoCD repo-server pod in CrashLoopBackOff

Known issue and resolution for the argocd-repo-server pod entering CrashLoopBackOff state in Automation Suite.

Description

In certain scenarios, the argocd-repo-server pod enters a CrashLoopBackOff state. As a result, Automation Suite services go into OutOfSync because ArgoCD cannot pull the desired chart from the repository.

The following error appears in the pod logs:

ln: failed to create symbolic link '/var/run/argocd/argocd-cmp-server': File exists

Cause

This is a known upstream ArgoCD issue. The copyutil init container attempts to create a symbolic link at a path where one already exists.

For details, refer to the upstream issue report argoproj/argo-cd#26595.

Solution

1. Confirm the issue by checking the logs of the argocd-repo-server pod:

   kubectl logs argocd-repo-server -n argocd -c copyutil
   

   If the output includes ln: failed to create symbolic link '/var/run/argocd/argocd-cmp-server': File exists, the issue is confirmed.

2. Restart the argocd-repo-server pod.