From: armando-migliaccio <armamig@gmail.com>
Date: Fri, 7 Mar 2014 21:11:20 +0000 (-0800)
Subject: NSX: fix nonsensical log trace on update port
X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=044d6a290d70bb22260fe8a1cdf35b96619263be;p=openstack-build%2Fneutron-build.git

NSX: fix nonsensical log trace on update port

Having this at a WARN level makes no sense, especially
because the actually message does not say anything about
a warning condition. Probably a brain fart of some sort.
Make it DEBUG, just because it may come handy to see what
data we're passing.

Change-Id: Ie667018faae587a3adb6b3edda4d9912344cae83
---

diff --git a/neutron/plugins/vmware/plugins/base.py b/neutron/plugins/vmware/plugins/base.py
index 2b832d132..b1b3a06e9 100644
--- a/neutron/plugins/vmware/plugins/base.py
+++ b/neutron/plugins/vmware/plugins/base.py
@@ -1287,7 +1287,7 @@ class NsxPluginV2(addr_pair_db.AllowedAddressPairsMixin,
             self._delete_port_queue_mapping(context, ret_port['id'])
             self._process_port_queue_mapping(context, ret_port,
                                              port_queue_id)
-            LOG.warn(_("Update port request: %s"), port)
+            LOG.debug(_("Updating port: %s"), port)
             nsx_switch_id, nsx_port_id = nsx_utils.get_nsx_switch_and_port_id(
                 context.session, self.cluster, id)
             # Convert Neutron security groups identifiers into NSX security