Avoid excessive ovsdb log statements

[ovsdb.git] / southbound / southbound-impl / src / main / java / org / opendaylight / ovsdb / southbound / ovsdb / transact / TerminationPointUpdateCommand.java

diff --git a/southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointUpdateCommand.java b/southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointUpdateCommand.java
index ada83a02243db759926f25f395e298013fe266c6..2e4a1689a1a36eb470bda51306264010bcfcf1dc 100644 (file)
--- a/southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointUpdateCommand.java
+++ b/southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/ovsdb/transact/TerminationPointUpdateCommand.java
@@ -127,7 +127,7 @@ public class TerminationPointUpdateCommand implements TransactCommand {
                     transaction.add(op.update(port)
                         .where(extraPort.getNameColumn().getSchema().opEqual(terminationPoint.getName()))
                         .build());
-                    LOG.info("Updated Termination Point : {}  with Uuid : {}",
+                    LOG.debug("Updated Termination Point : {}  with Uuid : {}",
                         terminationPoint.getName(), terminationPoint.getPortUuid());
                 }
             } else {