Open LS80 opened 3 years ago
Hello! Has there been any resolution for this?
Hi! Any chance this might get looked into some time soon as the issue is persisting?
I am running into this issue as well. Really hurts the ability to leverage app of apps pattern with sync-waves. Feels like this issue deserves more attention given its impact.
Looks like maybe we need a better health check: https://github.com/argoproj/argo-cd/issues/10550#issuecomment-1251088236
Probably related to the fact that an Argo CD App can consider itself "healthy" even though it's not intuitively in a healthy state: https://github.com/argoproj/argo-cd/issues/10088
Describe the bug
The health status of a parent app is briefly 💚 when a child app has status "missing". This becomes "progressing" as soon as the child application changes from "missing" to "progressing". This means that applications with a higher sync wave number start syncing before they should.
To Reproduce
Follow the instructions at https://argoproj.github.io/argo-cd/operator-manual/health/#argocd-app to add the recommended custom health check.
Add the repository https://github.com/LS80/argocd-app-of-apps
Run this
Observe the health status changes of
ls-sync-wave-issue
.Expected behavior
The parent application should not have a 💚 status until all child applications are 💚 .
Screenshots
⬇️
⬇️
⬇️
⬇️
Version