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
Describe the bug
When a change is pushed while a sync is already in progress, ArgoCD does not trigger a new sync after the initial sync completes, leaving the application in an out-of-sync state.
We don't use selfHeal, only auto-sync is enabled.
To Reproduce
Push a change to an application with auto-sync enabled.
Wait for ArgoCD to detect the change and start syncing.
While the sync is still in progress, push another change.
Once the initial sync completes, check the application status.
The application remains out-of-sync, and ArgoCD does not trigger an automatic sync for the second change.
After the sync from the step 2 finishes, the app will not be auto-synced despite being out-of-sync.
Expected behavior
ArgoCD should detect the subsequent change and automatically trigger a new sync after the previous one completes.
Version
argocd: v2.9.2+c5ea5c4.dirty
BuildDate: 2023-11-20T18:19:13Z
GitCommit: c5ea5c4df52943a6fff6c0be181fde5358970304
GitTreeState: dirty
GoVersion: go1.21.4
Compiler: gc
Platform: darwin/arm64
argocd-server: v2.13.1+af54ef8.dirty
BuildDate: 2024-11-21T11:07:47Z
GitCommit: af54ef8db5adfa77a08d4d05b1318a2198084c22
GitTreeState: dirty
GoVersion: go1.23.3
Compiler: gc
Platform: linux/amd64
Kustomize Version: could not get kustomize version: exec: "kustomize": executable file not found in $PATH
Helm Version: v3.16.2+g13654a5
Kubectl Version: v0.31.0
Jsonnet Version: v0.20.0
The text was updated successfully, but these errors were encountered:
Checklist:
argocd version
.Describe the bug
When a change is pushed while a sync is already in progress, ArgoCD does not trigger a new sync after the initial sync completes, leaving the application in an out-of-sync state.
We don't use
selfHeal
, onlyauto-sync
is enabled.To Reproduce
The application remains out-of-sync, and ArgoCD does not trigger an automatic sync for the second change.
After the sync from the step 2 finishes, the app will not be auto-synced despite being out-of-sync.
Expected behavior
ArgoCD should detect the subsequent change and automatically trigger a new sync after the previous one completes.
Version
The text was updated successfully, but these errors were encountered: