From e7bc52d3f2ed783864984e021eb9d676a55943c7 Mon Sep 17 00:00:00 2001
From: Dan Smith <danms@us.ibm.com>
Date: Sat, 9 Feb 2013 09:51:40 -0500
Subject: 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
---
 nova/exception.py | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'nova')

diff --git a/nova/exception.py b/nova/exception.py
index ede512a97..0ff485f9b 100644
--- a/nova/exception.py
+++ b/nova/exception.py
@@ -1115,3 +1115,8 @@ class InstanceRecreateNotSupported(Invalid):
 class ServiceGroupUnavailable(NovaException):
     message = _("The service from servicegroup driver %(driver) is "
                 "temporarily unavailable.")
+
+
+class DBNotAllowed(NovaException):
+    message = _('%(binary)s attempted direct database access which is '
+                'not allowed by policy')
-- 
cgit