Argocd manifest diff shows no differences even though image was updated and desired is different then live. about argo-cd HOT 10 CLOSED

@abhay-apella does it catch the diff if you do a hard refresh manually? I suspect you're having an issue with the cache.

from argo-cd.

@abhay-apella does it catch the diff if you do a hard refresh manually? I suspect you're having an issue with the cache.

We also tried clicking refresh, sync, and attempted manually updating values supplied. It only updated when we manually changed the spec.containers.image value or deleted the deploy. Would there be another thing to try to check if its a caching issue?

from argo-cd.

Hello, we are facing the same issue after upgrading from helm chart version 6.7.18 to 6.8.1.
Clicking on Hard refresh does make argocd see the diff to sync. Without manually doing a hard refresh, changes on image tag are never seen.

This bug looks like it came with argocd version 2.11.0

from argo-cd.

Hi,
We are going to try to upgrade to 2.11.2 to see if its resolved there. Was there any updates on the root cause? Alternatively is there any place we could take a look at to begin to see why this issue is caused?

Thanks!

from argo-cd.

An upgrade to 2.11.3 did not change the behavior. We still see a bug where the live and desired manifest are different but considered in sync. A hard refresh does not resolve it.

from argo-cd.

Hello guys.
My ArgoCD version is v2.11.3+3f344d5
and i have trhe same issue
this is my Argocd manifest file

--- apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: backend-application-dev namespace: argocd annotations: argocd-image-updater.argoproj.io/image-list: armaa/de_k8s:development argocd-image-updater.argoproj.io/write-back-method: git argocd-image-updater.argoproj.io/git-branch: development argocd-image-updater.argoproj.io/git-repo: [email protected]:dtf/dedge.git argocd-image-updater.argoproj.io/git-path: argocd/environments/development spec: project: default source: repoURL: 'https://github.com/def/dge' targetRevision: development path: 'argocd/environments/development' destination: server: 'https://kubernetes.default.svc' syncPolicy: automated: prune: true selfHeal: true syncOptions: - CreateNamespace=false - Validate=true - PrunePropagationPolicy=foreground - PruneLast=true

  Maybe somebody can help ?

from argo-cd.

In Argocd Gui i can see what my main deployment comteiner see new Doker image Digest but dont update pods

from argo-cd.

I seem to have the same issue on 2.11.3

from argo-cd.

We have discovered the specific issue causing our problem. The cluster also runs argo rollouts and there was an argocd configmap configuration for ignore differences on Rollouts:

resource.customizations.ignoreDifferences.all: |
    group: argoproj.io
    jsonPointers:
      - /spec/template/spec/containers/0/image
      - /spec/template/metadata/labels
    kind: Rollout

This should have only affected Rollout resources but it seems it also affected Deployments.

from argo-cd.

Closing this since it was a misconfiguration https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/#system-level-configuration

from argo-cd.