Deployment of Litmus through ArgoCD is causing Chaos Workflows to remain in a Pending State, thereby preventing them from running.
Vineeth-varma opened this issue · 1 comments
What happened:
I've deployed Litmus on a Google Kubernetes Engine using ArgoCD with helm charts litmus[3.8.0] and litmus-agent[3.8.2]. Although all my workloads are operating properly without any errors or issues, I'm encountering a problem where all my Chaos experiment runs remain in a pending state and never transition to the running state.
GKE Version: 1.27.14-gke.1042001
Argocd Version: v2.10.9+c071af8
Chaos-Experiments Image
Subscriber Logs
The logs from the Subscriber clearly indicating that the experiment is being created, however, it does not proceed to the running state.
What you expected to happen:
I want the experiments to execute seamlessly, without getting stuck in a queued or pending state.
Where can this issue be corrected? (optional)
How to reproduce it (as minimally and precisely as possible):
I manually triggered the workflow using the kubectl apply command, after removing the "workflows.argoproj.io/controller-instanceid: " label. As a result, the experiment ran smoothly. However, this information was not logged in the Litmus user interface.
Anything else we need to know?:
When I run the deployment locally using a direct Helm installation, everything works correctly. However, I encounter issues when deploying via ArgoCD, specifically with experiments getting stuck. I would appreciate if you could attempt to replicate this problem by deploying through ArgoCD.
hi @Vineeth-varma did you get this issue #4786 while installing via argocd ?