Git errors after changing RepoURL in ApplicationSet/Application

[bugspencor]

Our Git was migrated so I changed the RepoURL of the ApplicationSet. ArgoCD shows the correct RepoURL in the Applications and also sees the new commits in the new repo, but when syncing the app I get error messages:

Unable to load data: error acquiring repo lock: failed to initialize repository resources: rpc error: code = Internal desc = Failed to checkout revision d290...21a1: git fetch origin d290...21a1 --tags --force --prune failed exit status 1: error: Server does not allow request for unadvertised object d290...21a1

Only when pushing the changes to the old git repo the sync works. So somewhere ArgoCD seems to still use the old repository. I already hard refreshed the Applications and deleted all ArgoCD pods (in no specific order though).

I did not find something in the documentation how to change the RepoURL. Is it supported and are there any specific steps to do?

[fire2]

Same situation here, but I'm getting these errors:

Unable to load data: error acquiring repo lock: failed to initialize repository resources: rpc error: code = Internal desc = Failed to checkout revision f1bbcf2580f942cd5b4fb48e75e9821226470a95: git fetch origin f1bbcf2580f942cd5b4fb48e75e9821226470a95 --tags --force --prune failed exit status 128: fatal: remote error: upload-pack: not our ref f1bbcf2580f942cd5b4fb48e75e9821226470a95

[ntqp97]

Same situation here. Has anyone handled these errors?
Unable to load data: error acquiring repo lock: failed to initialize repository resources: rpc error: code = Internal desc = Failed to checkout revision 7dcf0c5fc60cba07a3774614757ad8df64ea00d2: git fetch origin 7dcf0c5fc60cba07a3774614757ad8df64ea00d2 --tags --force --prune failed exit status 128: fatal: remote error: upload-pack: not our ref 7dcf0c5fc60cba07a3774614757ad8df64ea00d2

[jmmclean]

For anyone else running into this issue - I was able to resolve it by doing a rolling restart of my argocd-redis-ha-server statefulset

[guemi]

Yeah @NiklasRosenstein that's exactly why.

Once you've done enough changes that Argo stops tracking those (I think it's 10 by default), you'll get rid of the error.

[fire2]

in my case I just edited the app resource in Kubernetes and updated the repository name / GH URL in the history section and that got rid of the errors.

[NiklasRosenstein]

I let Codex whip up a script to replace the repoURL in revisions or drop revisions matching the old URL: https://gist.github.com/NiklasRosenstein/18df5b13892b2d4b3195de896179c31b

Replacing the URL should be fine if the repository just got renamed but the revs are still valid.

[jmmclean]

Yea, circling back to this, I wonder if my history with the old URL was eventually overwritten and it just happened to coincide with when i did a redis restart

I've been killing the apps (non cascade) and letting our app of apps recreate them which resolves it

[jmmclean]

ok...I also learned that hitting sync (not refresh) on the app resolved my issue