Crash following db instance deletion
Bug #1926928 reported by
Andrew Bogott
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
trove-dashboard |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Usually (but not always) after I delete a database instance, the dashboard triggers an unhandled exception. This results in an unhelpful "Something went wrong!" page.
Changed in trove-dashboard: | |
status: | New → Fix Released |
To post a comment you must log in.
The stack trace suggests this is happening in a self._extra_ data(instance) . Either we're using an invalid cache of existing db instances or there's a race where the instance exists when the list is created but deleted before we get to the _extra_data() call.