(Failed?) migration from Angular. An unexpected error happened: TypeError: u.$$childHead is undefined

Not sure, maybe creating the same dashboard. Sorry I'm not very skilled neither in grafana nor in reporting bugs. May I downgrade grafana and copy relevant info from the panel?

Is the bug inside a dashboard panel?

Yes, but panel menu won't open

Environment (with versions)?

Grafana: v11.1.0 (5b85c4c2fc) I can try to update it

OS: Debian GNU/Linux Stable (Bookworm)

Browser: Firefox 128.0.3

Grafana platform?

A package manager (APT, YUM, BREW, etc.)

Datasource(s)?

No response

tonypowa commented 3 weeks ago

This issue is a test copy of an issue in another repo. Original issue: https://github.com/grafana/grafana/issues/#91075

moxious commented 3 weeks ago

Hi tonypowa, it seems like you're experiencing an issue with panel migration in Grafana after updating to a newer version. This could be related to a known issue with deprecated Angular panel support. Consider reporting this to the Frontend Platform project as they handle the migration and runtime of the Grafana UI which ties into panel functionality.

Before reporting there, you could also try the following steps to narrow down the problem:

If possible, replicate the issue on a non-production Grafana instance and see if all panels fail to migrate or only specific ones.
Check the Grafana logs for more detailed errors around the time you access the problematic panels.
If you have the option, try updating to the latest Grafana version to see if the issue persists, as it may have been addressed in a newer release.

Please include the steps you've tried and any additional information when transferring this issue to the Frontend Platform project.

moxious commented 3 weeks ago

Summary: Issue 400 is an open bug where some panels failed to migrate from Angular, resulting in an 'undefined' TypeError when the user attempts to access their menus. The bug started appearing after an update to Grafana v11.1.0, and the user is unsure how to reproduce it accurately but suggests it may be related to the dashboard creation process and is requesting help to possibly revert to an older version of Grafana.

moxious commented 3 weeks ago

Elaboration:

Hi @tonypowa, thank you for reporting the issue you're facing after migrating from Angular in Grafana. To help us better understand and address the problem, could you please provide us with more information? Here's a list of details that would be helpful:

Can you share the specific steps you took during the migration that led up to encountering the error? Details on how you triggered the migration would be beneficial.
Is there any console output or log messages that appear alongside the error message you've provided? If so, please include them.
You mentioned that the issue occurs when trying to open the panel menu. Can you provide a screenshot or video of what happens when you attempt to do so?
Is it possible for you to share an export of the dashboard configuration that's causing issues (with sensitive information redacted)?
You mentioned considering a downgrade to copy relevant information from the panel. If safe and possible, could you try doing that and see if any pertinent details become evident when comparing the versions?

Any additional context around the actions you took immediately before the issue appeared could also be helpful in diagnosing the problem. Once we have these details, we'll be better positioned to assist you. Thank you!

moxious / triage