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
Our setup uses Argo-CD applications deployed using ApplicationSets on an app of apps pattern. Applications are multisource, i.e. using git generator and Helm Chart (OCI) + Values (Git repo). We currently do not have Auto-Sync enabled.
On our development environment, our Helm Charts artifacts are created and pushed to the OCI registry using rolling tags with "-dev" suffix, e.g. 0.0.1-dev. We overwrite the artifact with same tag upon new CI build completion.
We are currently running ArgoCD 2.11.4 and after upgrading to version 2.12.x (tried 2.12.1-3), an application running a chart with version 0.0.1-dev and upon the creation of a new chart with same tag version including changes, the changes are detected by Argo (application marked Out-Of-Sync) but the resources that are marked as Out-of-Sync cannot be synced any longer using the "Sync" button. However, if we enable "Auto-Sync" for the application the resources are synced as expected.
Additionally, performing a "Sync" with resource replacement recreates the resources but of previous state, still out of sync.
When the Helm Chart is updated to a different version tag, e.g. 0.0.2-dev there is no issue. It may be related on how the artifacts are cached. If we restart the Redis pods the first sync works but from there on we have the same above described behaviour.
To Reproduce
Create and deploy an ArgoCD application which uses an OCI helm chart and a values file on a git repo.
Update the Helm Chart with some changes and push the chart to the OCI registry using the same tag.
Confirm that ArgoCD detects new chart (force with Hard Refresh) and application is marked Out-Of-Sync.
Try to perform a manual full sync of the application.
Expected behavior
Triggering a Sync using the UI should sync the resources to the latest state and not remained unapplied.
tromsosec
changed the title
Upgrade to 2.12.x sync of out-of-sync resource no longer working.
After upgrade to 2.12.x, sync of "out-of-sync" resources no longer working.
Sep 17, 2024
Checklist:
argocd version
.Describe the bug
Our setup uses Argo-CD applications deployed using ApplicationSets on an app of apps pattern. Applications are multisource, i.e. using git generator and Helm Chart (OCI) + Values (Git repo). We currently do not have Auto-Sync enabled.
On our development environment, our Helm Charts artifacts are created and pushed to the OCI registry using rolling tags with "-dev" suffix, e.g. 0.0.1-dev. We overwrite the artifact with same tag upon new CI build completion.
We are currently running ArgoCD 2.11.4 and after upgrading to version 2.12.x (tried 2.12.1-3), an application running a chart with version 0.0.1-dev and upon the creation of a new chart with same tag version including changes, the changes are detected by Argo (application marked Out-Of-Sync) but the resources that are marked as Out-of-Sync cannot be synced any longer using the "Sync" button. However, if we enable "Auto-Sync" for the application the resources are synced as expected.
Additionally, performing a "Sync" with resource replacement recreates the resources but of previous state, still out of sync.
When the Helm Chart is updated to a different version tag, e.g. 0.0.2-dev there is no issue.
It may be related on how the artifacts are cached. If we restart the Redis pods the first sync works but from there on we have the same above described behaviour.
To Reproduce
Expected behavior
Triggering a Sync using the UI should sync the resources to the latest state and not remained unapplied.
Screenshots
Version
argocd@argo-cd-argocd-application-controller-0:~$ argocd version argocd: v2.12.3+6b9cd82 BuildDate: 2024-08-27T11:57:48Z GitCommit: 6b9cd828c6e9807398869ad5ac44efd2c28422d6 GitTreeState: clean GoVersion: go1.22.4 Compiler: gc Platform: linux/amd64
Logs
ApplicationController logs when manual resources sync is triggered:
Kubernetes ArgoCD Deployment
The text was updated successfully, but these errors were encountered: