Refresh Failed: can not refresh repository which contains submodules cause argocd modified some files about argo-cd HOT 2 OPEN

@agaudreault
Thanks for your kind response. Recently, we've been experimenting with using git submodules to deploy our production environment, aiming to prevent developers from accessing sensitive production configuration files. And our kustomization.yaml did not specify a namespace because our pre-production and production environments are on the same Kubernetes cluster, so we configure namespace in Web UI. This bug seems quite clear: argocd modified the kustomization.yaml, causing the git submodule checkout to fail and displaying Unable to checkout '8315e94e5dbebe05e52301252cd7ac76b3298539 at Last Sync on the page. Now we solved this problem by these following steps:

1. Explicitly specifying the namespace in the kustomization.yaml file;
2. Adding a newline at the end of each file.

I think argocd should rollback modifitions before updating submodule.

from argo-cd.

Hey @tanyaofei, do you have any other logs on the repo-server components when it tries to generate your application? And can you share your Application manifest to help reproduce the issue.

Also, can you clarify

Argocd refresh will modify kustomization.yaml, such as adding new line at end of file, or adding namespace field in kustomization.yml if I config namespace in the Web UI.

What is done in the Web UI exactly?

And last question, is that a new error after an upgrade, did anything change recently in your deployment or it has always been like this?

from argo-cd.