DEV Community

When It Runs
When It Runs

Posted on Originally published at whenitruns.substack.com

When Argo CD's `manifest-generate-paths` Auto-Sync Runs Past a Mid-Sync Commit

Argo CD v3.5.3: a path-changing commit compared during a sync stayed OutOfSync after it with selfHeal off, and with selfHeal on went in as a partial sync with no PreSync hook or history entry.

When It Runs — Run Report #RR15 · Testing what infrastructure actually does.

Provider · Component: Argo CD · the application controller's automated sync for Applications with the argocd.argoproj.io/manifest-generate-paths annotation — what happens to a commit that changes the application's path when it is compared while a sync is still running, with selfHeal off and on

Versions tested: measured — Argo CD v3.5.3 (the latest release as of 2026-09-28; v3.5.4, v3.5.5, v3.5.6, v3.5.7, v3.6.0 and v3.6.1, released on 2026-10-06, 2026-10-12, 2026-10-20, 2026-11-02, 2026-11-03 and 2026-11-04, were not measured), a single version. source-read — controller/state.go, controller/appcontroller.go, controller/sync.go and gitops-engine/pkg/sync/sync_context.go at the same tag, and controller/appcontroller.go at v3.4.9, whose automated-sync call is the same. The 3.3 line was not measured.

Config profile: a single-node kind cluster (kind v0.30.0, node kindest/node:v1.33.4, digest-pinned; v1.33 is on the list of Kubernetes versions tested with Argo CD 3.5) on a dedicated test VM; the official install.yaml for v3.5.3 applied server-side; the application controller's log level at debug; a local Git server with one repository and three application paths, each holding a ConfigMap and a PreSync hook Job that runs for 60 seconds; three automated Applications with targetRevision: HEAD — P1 with the annotation and selfHeal off (its default), P2 with the annotation and selfHeal on, P3 without the annotation (control); a commit B that changes all three paths, pushed while the syncs to commit A are held by their hooks, followed by a manual refresh of each Application; each Application polled every 5 seconds for 360 seconds after its sync to A finished.

Verified on: 2026-11-16 (desk sources re-checked; v3.6.1 was the latest release) · lab measured 2026-09-28 on Argo CD v3.5.3.

Affects: Argo CD v3.5.3 — and, by the source, v3.4.9, whose automated-sync call is the same — Applications with automated sync and the manifest-generate-paths annotation, when a commit that changes the application's path is compared while a sync is still running: with selfHeal off, the commit was not auto-synced in the 360 seconds after that sync, and the Application stayed OutOfSync; with selfHeal on, the commit was applied by an automated partial sync — an operation that listed resources — without its PreSync hook running and without a history entry.

TL;DR: On Argo CD v3.5.3, when a commit that changed an automated Application's path arrived while the Application was still syncing, the Application with the manifest-generate-paths annotation and selfHeal off did not auto-sync the commit and stayed OutOfSync, and with selfHeal on it applied the commit as a partial sync, without its PreSync hook and without a history entry — while the same Application without the annotation synced the commit in full.

Full report: https://whenitruns.substack.com/p/when-argo-cds-manifest-generate-paths

Reproduction repo: https://github.com/whenitruns/when-argo-cds-manifest-generate-paths-auto-sync-runs-past-a-mid-sync-commit

Top comments (0)