dashboards imported via relation are not imported in all orgs

Bug #1883020 reported by Andrea Ieri
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Grafana Charm
Won't Fix
Medium
Unassigned

Bug Description

When a new dashboard is provided by a related charm, it is only imported in the main org; if you have created other orgs manually the new dashboard will need to be exported/imported by an operator.

I think new dashboards should be propagated to all orgs by default.

Also note related bug 1745654

Tags: bseng-34
Edin S (exsdev)
Changed in charm-grafana:
importance: Undecided → Wishlist
Edin S (exsdev)
Changed in charm-grafana:
importance: Wishlist → Medium
Changed in charm-grafana:
status: New → Triaged
Revision history for this message
Drew Freiberger (afreiberger) wrote :

I saw this happen on a site where the dashes imported into the second org, but not the original org. I think this is related to changes around tagging the folder based on the model that provided the dashboards.

Alvaro Uria (aluria)
tags: added: bseng-34
Eric Chen (eric-chen)
Changed in charm-grafana:
status: Triaged → Won't Fix
Revision history for this message
Paul Goins (vultaire) wrote :

Is there a reason behind marking this as won't fix? We're actively having to fix this during each handover since the charm isn't doing this for us.

I'm moving this to "confirmed", at least for now.

Changed in charm-grafana:
status: Won't Fix → Confirmed
Revision history for this message
Paul Goins (vultaire) wrote :

Ahh - grafana-k8s is the new charm. Indeed, wontfix because this is for the old LMA stack.

Changed in charm-grafana:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.