nova-compute raises non-existent exception on failed DB access

Bug #1120390 reported by Dan Smith
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Dan Smith

Bug Description

Apparently the DBError exception disappeared from nova/exception.py, but nova-compute still tries to use it.

Dan Smith (danms)
Changed in nova:
importance: Undecided → High
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/21569

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/21569
Committed: http://github.com/openstack/nova/commit/e7bc52d3f2ed783864984e021eb9d676a55943c7
Submitter: Jenkins
Branch: master

commit e7bc52d3f2ed783864984e021eb9d676a55943c7
Author: Dan Smith <email address hidden>
Date: Sat Feb 9 09:51:40 2013 -0500

    Fix nova-compute use of missing DBError

    Apparently exception.DBError disappeared at some point, but nova-
    compute was still using it. Since it was a stretch in the first
    place, and nothing else in exception.py looks reasonable, this
    adds exception.DBNotAllowed.

    Fixes bug 1120390

    Change-Id: Ifbfa0b09f3dc011ad87f6f3b06eb0fdaa7247ec0

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-3 → 2013.1
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.