Open Hargeek opened 3 weeks ago
Hmmm, you have your application configured to auto-sync with the configuration
syncPolicy:
automated:
prune: true
selfHeal: true
allowEmpty: false
But you are also calling an argo API to perform the sync. My guess would be that sometime auto-sync triggers automatically around the same time you request the sync. I think logs of the application-controller would be required to know which sync is not using the correct commit ID. I assume targetRevision: '{{ source.targetRevision }}'
resolves to targetRevision: cicd
. Is this a branch or a tag that is updated?
**Checklist:
argocd version
.I use the method provided by "github.com/argoproj/argo-cd/v2/pkg/apiclient/application" to synchronize the application.
Now I find that sometimes two records are generated almost at the same time. The record with the larger the id is the old version, which leads to the invalidity of the synchronization call. This situation is not inevitable. Sometimes it will happen.
We can only wait for the next synchronization, so that I can't realize the purpose of real-time synchronization after the git repository is modified. Please help me see what the reason is.
I tried version 2.4.3 and version 2.11.4, both are like this
I used the git generator to configure my app. The relevant definitions are as follows
Version