-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
field enforce_metric_name not found using latest loki 3.0.0 #12594
Comments
@fragolinux I am getting the same error, guess the field has been removed? |
Let's wait for help |
Could be related: #2096 |
FYI the config option |
@JStickler thanks for the confirmation. I can confirm that removing this field does solve the issue. It would be nice if this was part of your helm chart upgrade page. Are there any other fields like this we should be aware of? |
problem is that this is a brand new deploy, on a clean cluster... we had to change loki image from 2.6.1 to 3.0.0 as 2.6.1 (default in chart) caused crashbootloop, and that parameter was in the config as put there by the chart, so how to "remove" it? |
Thanks for confirming.
I will add it to my To Do list.
A lot of the work that was done late last summer and autumn involved removing unused or deprecated code. Everything that was thought to be a breaking change was documented in the upgrade guide. This must have been missed somehow.
Can you manually edit your |
But as everything is managed by flux, if I do so, on next of its reconcile loops, it will put it back... |
i removed that line from the "loki" configmap, and now i get this in the logs of the read pods, while the write ones seem now ok:
always using loki 3.0.0 with latest chart, of course... and btw, i can't just remove that line, i had to suspend flux to prevent reconcile, but i cant' leave it that way, field should not be added to that cm by the chart itself... |
sorry, found the problem... we were using the chart v3.0.0, with the values of the latest one... here our working helmrelease, with chart v6.2.0... we can close this, thanks!
|
solution found, above, thanks |
Describe the bug
deployed loki v3.0.0 and got in its pods the error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
pods starting up
Environment:
Screenshots, Promtail config, or terminal output
used this flux helmrelease:
strangely we had to specify this, too, as helm previously complained about missing or wrong version crds (it complained about missing podLogs v1alpha1, which by default should be disabled, as under selfmonitoring section)... why is this needed if by default it's disabled???
an other problem of the actual chart is that it still tries to install loki with image version 2.6.1, which causes crashloop... fixing image 3.0.0 in the helmrelease, fixed the problem
The text was updated successfully, but these errors were encountered: