-
Notifications
You must be signed in to change notification settings - Fork 172
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
fix: stage reconciler failures if cache is stale #1475
Conversation
✅ Deploy Preview for docs-kargo-akuity-io ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Soumya Ghosh Dastidar <gdsoumya@gmail.com>
5bb6f67
to
0a9a1ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good as a workaround, but I will also investigate the underlying issues in controller runtime.
@krancour log dump where I encounter the situation :
The stage was reconciled and promoted, but then when it came to running verification stage it checks stage but sees current freight as empty : Because I am running my change a manual refresh or an eventual resync after resync duration will trigger the verification. In the above case it was a manual refresh from UI |
Sometimes the controller cache for stages is stale and doesn't show updated result of a promotion leading to a situation where CurrentFreight is nil temporary and so it sets the phase as NotApplicable. But in reality the CurrentFreight is already updated in live state but because the controller has now patched the phase as not applicable any future reconciliations completely skip the verification step as phase doesn't match the required value.