-
Notifications
You must be signed in to change notification settings - Fork 2
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
Flux automation released untagged image #1905
Comments
It straight away corrected it in the next automation run, but it is strange indeed that it did it in the first place. |
another one, this time for grafana (the earlier one was scope). |
The logs show fluxd straight-up deciding that the untagged image is the right one:
This suggests to me that it's getting bogus information from the cache; either a bug in the code that assembles the available images when automation asks, or a bug in the metadata fetching and storing. Asking LIstImages directly doesn't yield a suspicious result, but it has been updated several times since it the problem occurred. |
We've seen this in the sock shop too, so users will likely run into it as well. |
See fluxcd/flux#1051 |
First time this appears to have happened is https://github.com/weaveworks/service-conf/commit/d4b2a9775, according to
|
Full list, showing the commit dates too:
Sometimes happens a few times on a day, sometimes doesn't happen for about a month :/ |
The registry rewrite (fluxcd/flux#851) was merged not long before the first such commit, as were fluxcd/flux#876 and fluxcd/flux#880, which were follow-ons from that. It's likely the problem lies in those, somewhere. |
There is good chance this got fixed by fluxcd/flux#1251 |
We haven't seen it since. -> closing |
https://github.com/weaveworks/service-conf/commit/01bb051
The text was updated successfully, but these errors were encountered: