Fix incorrect trace log in FRM 42/1642/3
authorAlessandro Boch <aboch@cisco.com>
Thu, 3 Oct 2013 12:17:13 +0000 (05:17 -0700)
committerGerrit Code Review <gerrit@opendaylight.org>
Thu, 3 Oct 2013 23:42:48 +0000 (23:42 +0000)
commit8fcb3ad33b7d0dae547c48fd57dcadc1488d91db
treeaeec29f568410d6bbf0cedd1b6bc8e75ca3437cf
parent349f16b51b3956ac46cbe3e0d8cb4a5b604efa34
Fix incorrect trace log in FRM

ISSUE: Log reports failure on opposite action, makes it hard to debug
CHANGE: Also lowering severity from warn to trace for some flow programming logs

Change-Id: If8f59137ccd2539b7d46019d0095b2cb2336fb57
Signed-off-by: Alessandro Boch <aboch@cisco.com>
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java