-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same image is updated multiple times, 1.20 --> 1.20.0 --> 1.20 --> 1.20.0 #375
Comments
From a semver perspective, 1.20.0 and 1.20 are the same versions, but I agree, the result for such situations should be stable and predictable. As a workaround, you probably want an additional |
Thanks, it works fine using the workaround! It seems to be an intermittent issue as it at one point stopped updating back and forth some days back (I was not at work so no one touched the system explicitly). But logs still said the following every 2-6th iteration:
Dug a bit more and found the previous replica which didn't have any pods, but ArgoCD still insisted it had a pod in processing state. After deleting the rs it quited down and with the workaround everything looks normal. |
I get this behaviour from the Docker hub image "sensu/sensu" (monitoring) |
I am seeing this exact behavior. We tag with major, major.minor, and major.minor.patch with every release. I am watching argocd loop between 1.4 and 1.4.0 over and over. |
Don't know if it's related of if i have to open another issue, but when trying to update images like docker.io/traefik:~2 there is a loop between the numeric tag and the 'v' prefixed tag.
Argocd application configuration: metadata:
name: traefik
annotations:
argocd-image-updater.argoproj.io/image-list: docker.io/traefik:~2
argocd-image-updater.argoproj.io/traefik.update-strategy: semver
argocd-image-updater.argoproj.io/traefik.platforms: linux/arm,linux/amd64
argocd-image-updater.argoproj.io/write-back-method: git
argocd-image-updater.argoproj.io/write-back-target: kustomization
spec:
project: default
# Source of the application manifests
source:
repoURL: xxx
targetRevision: master
path: .
... Argocd v2.5.6+9db2c94 |
Seems like the image updater is stuck in a loop of updating the same image back and forth between the same version, 1.20 --> 1.20.0 --> 1.20 --> 1.20.0 etc
I have only seen it happen with this one image this far, and I have multiple other images that are tagged the same way. Image mask is :v1.x
ArgoCD Image updater: v0.11.3
ArgoCD: v2.2.4
Registry: Azure container registry
The text was updated successfully, but these errors were encountered: