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
[Bug] Go panic when syncing many dashboards #1498
Comments
That's certainly something interesting to investigate, thanks for reporting! |
The issue could be the error handling here : if the error is This happens in |
Probably a stupid question, but as this occurred during the first population of the dashboards to Grafana, why is onDashboardDeleted being called? |
@smuda Well, it's hard to say without seeing it in a lab, but it could potentially be in at least two cases:
|
Describe the bug
Sometimes there is a go panic which crashes the pod. It only seems to occur when there is many dashboards to sync (>60). When the pod is automatically restarted, a number of the dashboards are already synced and the sync can be completed.
The panic log
Version
5.8.0
To Reproduce
It seems hard to reproduce, but having many dashboard helps. To trigger the problem I restart the grafana pod (to have it empty) and then restart the operator pod after a few seconds. Then there is a full sync of all the dashboards and datasources.
Expected behavior
Not a crashing pod. :-)
Suspect component/Location where the bug might be occurring
The panic points to
github.com/grafana/grafana-operator/v5/controllers/dashboard_controller.go:312
, butI'd assume the problem is somewhere else, perhaps even in github.com/grafana/grafana-openapi-client-go
Runtime (please complete the following information):
The text was updated successfully, but these errors were encountered: