Skip to content
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

App sync fails with 'failed to compare revisions for source 1 of 2' when new source is introduced first #20900

Open
3 tasks done
DerekTBrown opened this issue Nov 21, 2024 · 2 comments
Labels
bug Something isn't working more-information-needed Further information is requested version:2.12 Latest confirmed affected version is 2.12

Comments

@DerekTBrown
Copy link

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

  • I successfully synced an application with a single source, a helm chart repo.
  • I subsequently added a second source, in index 0, a git repository.
  • When I sync the application, I get:

57563802-c076-413e-8346-4ea5d01a57ab

This indicates to me that ArgoCD is performing comparisons between each index in the source array (i.e. old[0] vs new[0]), instead of pattern matching between source repos/names when comparisons are performed.

To Reproduce

  1. Create an application with a single source, a helm chart repo.
  2. Sync the application.
  3. Add a second source, in index 0, a git repository.
  4. Attempt to sync the application.

Expected behavior

I would expect that ArgoCD would perform comparisons between sources with the same repositoryUrl, rather than naively comparing between source indexes.

Version

v2.12.4+27d1e64
@DerekTBrown DerekTBrown added the bug Something isn't working label Nov 21, 2024
@andrii-korotkov-verkada andrii-korotkov-verkada added the version:2.12 Latest confirmed affected version is 2.12 label Nov 21, 2024
@andrii-korotkov-verkada
Copy link
Contributor

We have this PR merged #20470. Do you think we can build on top of that for matching?

@andrii-korotkov-verkada
Copy link
Contributor

There's a bit of a blurry line between what constitutes the same source. For example, same url but different path can be a quite different source. Also, if we get a support for multiple sources with the same url, this match won't work well. I think matching by name can be good though. Let me know what you think.

@andrii-korotkov-verkada andrii-korotkov-verkada added the more-information-needed Further information is requested label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working more-information-needed Further information is requested version:2.12 Latest confirmed affected version is 2.12
Projects
None yet
Development

No branches or pull requests

2 participants