Closed matthew-s-walker closed 2 months ago
Thanks for pointing this out! It seems to be an issue with error propagation. We'll implement a fix for this soon
we are running into the same issue, thanks for raising this here. If any support is required to resolve this, please let me know!
Fixed in #1584 - will cut a release soon
@theSuess is there an estimate for when the next release will happen? We are still blocked by this issue.
Thanks a lot!
Hey, sorry for the late reply. I was at an offsite and did not have time to do the release. We're looking into finishing up nested folder support (only missing #1600 for the MVP) and will probably cut a release after that.
Describe the bug We're trying to set up GrafanaAlertRuleGroup resources in the same helm chart as the one which creates the Grafana resource. When we install the chart, the GrafanaAlertRuleGroup goes into a "NoMatchingFolder" state until you delete and recreate the alert resource. Setting the "resyncPeriod" to low values doesn't seem to get the resource out of this state in any reasonable time.
The issue is not reproducible when running against the "make start-kind" and "make run" setup (which is running a newer k8s version than we are), but it does reproduce when pointing a local operator at our EKS cluster. I imagine the difference in behaviour could be due to latency, or the fact that we have to modify the hostfile to point the "grafana-service.testnamespace" to 127.0.0.1 and run
kubectl port-forward
to allow the operator to connect to Grafana.Version v5.9.1
To Reproduce Steps to reproduce the behavior:
Expected behavior Either to begin with or after a resyncPeriod, the rule group should be properly reconsiled.
Suspect component/Location where the bug might be occurring The grafanaalertrulegroup_controller.go can be modified to retry finding the folder, which fixes the issue but I'm not confident that this is the best way to fix this:
Screenshots![screenshot](https://github.com/grafana/grafana-operator/assets/93143734/defb815b-7589-4727-b55d-38babc4be059)
Runtime (please complete the following information):