From: armando-migliaccio <amigliaccio@nicira.com>
Date: Fri, 15 Nov 2013 02:22:26 +0000 (-0800)
Subject: Lower severity of log trace for DB integrity error
X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=4c6906498a5ef0f11ada3ff2224e995f6b3062d8;p=openstack-build%2Fneutron-build.git

Lower severity of log trace for DB integrity error

LOG.exception is not appropriate, since a concurrent
port creation can occur and it has been dealt with
in the except block.

This avoids spooking users who are on the hunt for
real bugs.

Supports fix for 1239637

Change-Id: I9489702ee63db0b004fe41195fa4727af261d514
---

diff --git a/neutron/plugins/ml2/plugin.py b/neutron/plugins/ml2/plugin.py
index 4f7e55690..973a9fe14 100644
--- a/neutron/plugins/ml2/plugin.py
+++ b/neutron/plugins/ml2/plugin.py
@@ -425,7 +425,7 @@ class Ml2Plugin(db_base_plugin_v2.NeutronDbPluginV2,
             except os_db.exception.DBError as e:
                 if isinstance(e.inner_exception, sql_exc.IntegrityError):
                     msg = _("A concurrent port creation has occurred")
-                    LOG.exception(msg)
+                    LOG.warning(msg)
                     continue
                 else:
                     raise