-
Notifications
You must be signed in to change notification settings - Fork 164
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
Error notifications despite the resource being successfully reconciled #258
Comments
Please post here the output of |
Sure
|
I suspect it might be caused by two reconciliation happening at the same time: one set by HelmRelease's interval, second triggered by source update. I've seen the same issue but only from time to time, usually for me it's bunch of releases updated properly and one or two: first success then "object has been modified" error. Though I haven't seen such errors from Kustiomization, so maybe helm-controller treats already running reconciliation somewhat differently then kustomize-controller? Something similar is described in fluxcd/flux2#1882 could they be connected? |
It seems to be still happening. At least It happened in 1/2 of our clusters. Upgrade went through fine as described in this issue
|
This issue was first opened at fluxcd/flux#3480
Describe the bug
Flux sends out error level notifications despite the resource being successfully reconciled.
This is the discord notification I received, in that order:
And when I checked later:
All of this happened in a 2 minutes time window between the start of the reconciliation and the error notification.
To Reproduce
Hard to tell. No manual intervention was made besides updating the docker image in the values of the chart on the gitops repository, all those resources are managed by flux. Last time jellyfin was reconciled it worked fine. A week ago grafana reconciliation had the same error but not after so it does not seem to be related to a helm chart in particular.
My guess is that there is a conflict because flux tries to run two reconciliations at the same time of the same resource.
Expected behavior
Error notifications sent when reconciliation actually fails, maybe for a longer period of time? At least make this maybe a warning level on first occurrence.
I am not sure what should be done, but throwing an error seems wrong.
The text was updated successfully, but these errors were encountered: