Skip to content
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

Grafana cannot deploy with custom home dashboard #449

Closed
psycofdj opened this issue Jan 7, 2023 · 2 comments · Fixed by #450
Closed

Grafana cannot deploy with custom home dashboard #449

psycofdj opened this issue Jan 7, 2023 · 2 comments · Fixed by #450

Comments

@psycofdj
Copy link
Contributor

psycofdj commented Jan 7, 2023

Since version v27.2.0 and its upgrade to grafana 8.5.15, the post-start script fail for grafana

Task 369950 | 10:17:55 | L executing post-start: grafana/ff8ec6a4-ac9b-4222-9875-2a552b0d6b74 (0) (canary) (00:00:40)
                       L Error: Action Failed get_task: Task 3006e3aa-76f5-4619-76d4-24572f123766 result: 1 of 2 post-start scripts failed. Failed Jobs: grafana. Successful Jobs: bosh-dns.
Task 369950 | 10:18:01 | Error: Action Failed get_task: Task 3006e3aa-76f5-4619-76d4-24572f123766 result: 1 of 2 post-start scripts failed. Failed Jobs: grafana. Successful Jobs: bosh-dns.

After some investigation, the error occurs in the script /var/vcap/jobs/grafana/bin/grafana-homepage which use grafana API to:

  1. uploads a custom home dashboard given in the grafana.dashboards.custom_homepage_json property
  2. sets preferences to use this dashboard as home dashboad

Those api calls are made using the slugs endpoints which were deprecated in v7 and removed in v8.

@benjaminguttmann-avtq
Copy link
Contributor

So if I get it right this happens only if you have the grafana.dashboards.custom_homepage_json configured, right?

@psycofdj
Copy link
Contributor Author

psycofdj commented Jan 9, 2023

indeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants