You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've pasted the output of argocd version (grabbed from the server ui)
Describe the bug
When git repositories are down, argo-cd is unable to rollback even though the history is there. This is something that can be done in other tools like helm which preserves the revision local in the cluster. This makes it harder to revert app changes that coincidentally happen when the git repo is not accessible to ArgoCD.
To Reproduce
Deploy a kustomize app with ArgoCD and then cut communications with the git repo.
Expected behavior
ArgoCD rolls back the app based on the historical data preserved.
Screenshots
The error in the UI says:
Unable to rollback application: application spec for **** is invalid: InvalidSpecError: repository not accesible: .... repo client error while testing repository: rpc error = ... context deadline exceeded (Client.Timeout exceeded while awaiting headers).
Version
v2.13.1+af54ef8
The text was updated successfully, but these errors were encountered:
Checklist:
argocd version
(grabbed from the server ui)Describe the bug
When git repositories are down, argo-cd is unable to rollback even though the history is there. This is something that can be done in other tools like
helm
which preserves the revision local in the cluster. This makes it harder to revert app changes that coincidentally happen when the git repo is not accessible to ArgoCD.To Reproduce
Deploy a kustomize app with ArgoCD and then cut communications with the git repo.
Expected behavior
ArgoCD rolls back the app based on the historical data preserved.
Screenshots
The error in the UI says:
Version
v2.13.1+af54ef8
The text was updated successfully, but these errors were encountered: