-
Notifications
You must be signed in to change notification settings - Fork 72
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
Image Automation controller silently stops working #286
Comments
Same for us. but it alls seem to be go down to git level if i not mistaken. fluxcd/source-controller#439 (comment) |
@aholbreich There are two related problems:
I know you are seeing the log message, from the comment you linked -- are you also experiencing the second problem, that the controller stops doing anything? |
Hi, no. Not really seen controller problems. |
Same as #282. I will be updating that thread instead, here's the latest comment: |
Describe the bug
On our clusters, we had connectivity issues on Dec 26th. I noticed that since then, image automation failed to update (but ImagePolicies were up to date).
Here are the last logs for one of the controllers:
Since that point in time, the controller stopped working.
Killing the pod fixed this issue, but it'd be great if it could self-heal in this scenario?
Steps to reproduce
Expected behavior
The controller should try again to reconcile as the connectivity would have been resolved.
Screenshots and recordings
No response
OS / Distro
Ubuntu 20.04
Flux version
flux version 0.16.1
Flux check
N/A
Git provider
GitHub
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: