trove-dashboard

Crash following db instance deletion

Bug #1926928 reported by Andrew Bogott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
trove-dashboard
New
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.

Revision history for this message
Andrew Bogott (andrewbogott) wrote :

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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove-dashboard 17.0.0.0rc1

This issue was fixed in the openstack/trove-dashboard 17.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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