-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
argocd with crossplane: getting circular dependency warnings on each reconciliation attempt #11699
Comments
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
We also deploy crossplane using ArgoCD, and I am seeing these warnings as well. I'm not sure whether the issue has any implications or if it just an annoying log line. It seems like the circular dependency detection doesn't anticipate that a resource can have multiple ownership paths to the same parent/grandparent resource. It's an unfortunate family tree but one that ArgoCD should probably be able to handle. |
there is an attempt to fix that via #12667 |
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]>
This commit fixed an issue #11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes #11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue #11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes #11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue #11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes #11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue #11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes #11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]>
This commit fixed an issue argoproj#11699 that caused a warning even if the cycle didn't exist. Fix false cycle discovery by copying the visited resource map before recursively calling of getAppRecursive. Fixes argoproj#11699 Signed-off-by: Arata Furukawa <[email protected]> Co-authored-by: Blake Pettersson <[email protected]> Signed-off-by: Javier Solana <[email protected]> Signed-off-by: Javier Solana <[email protected]>
Checklist:
argocd version
.Describe the bug
every 180 seconds (a standard reconciliation interval) I'm getting few hundreds of unexpected warnings similar to one provided below
these errors are getting generated by the argocd-application-controller, relevant code is here:
https://github.com/argoproj/argo-cd/blob/v2.5.4/controller/cache/cache.go#L280
To Reproduce
Expected behavior
it would be great to find out what's going wrong here to be able to get rid of these warnings completely
Screenshots
here is an example of such a circular dependency composition
in this context Provider spec is referenced twice (from CRD and from ProviderRevision sides), I assume this is the reason to why argo-cd is throwing circular dependency warnings
Version
Crossplane version:
Kubectl version:
Logs
The text was updated successfully, but these errors were encountered: