Closed Bug 1296104 Opened 8 years ago Closed 7 years ago

re:dash dashboard 500 error

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: clarkbw, Assigned: robotblake)

Details

Hopefully this is useful. I don't have steps to reproduce this, it has only happened once so far.  Here's what happened.


I recently created the DevTools: By Country Dashboard.
https://sql.telemetry.mozilla.org/dashboard/devtools-by-country

Today I was adding widgets to the dashboard. (Chrome browser) There was a slow down when removing a widget and the widget wasn't actually removed before I continued; I didn't notice until later.  I tried adding another widget (which incidentally was the same widget but at double size).  The additional widget was added, however now I had two of the same widgets with just different sizes and in the wrong location.  I opened the dashboard editor to move the new widget up and the editor seemed to hiccup.  The dashboard never reloaded after that.

It now only gives me 500 errors.

It is easy enough to recreate the dashboard if the short term resolution is to just delete it.
Hey Roberto - this came in today after our scrub. Can you have someone on your team take a look at this? Rolled to P1 but did not swag effort.
Assignee: nobody → rvitillo
Priority: -- → P1
d'oh this should go to ops...
Assignee: rvitillo → bimsland
This appears to be an upstream bug where somehow "null" got inserted instead of the visualization id. Manually fixed in the database.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
I had this same issue happen again.  This time I was just in the edit the dashboard view and it seemed to time out.  Afterward I'm getting the same 500 error.  ( https://sql.telemetry.mozilla.org/dashboard/devtools-executive-dashboard )
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed the issue in the database again. Going to work on reproducing this and filing a bug upstream.
This should be fixed in the version that's deployed now, feel free to reopen if it occurs again.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.