From da8e575d92e57ff4c8a4cb616197ff8b3c698aff Mon Sep 17 00:00:00 2001
From: Bruno Dilly <bruno.dilly@intel.com>
Date: Wed, 2 Sep 2015 20:25:40 -0300
Subject: [PATCH] flow: just use a dbg message if fails to parse
 direction-vector

Just like all the other datatypes.
It was the last one providing an error msg.

Signed-off-by: Bruno Dilly <bruno.dilly@intel.com>
---
 src/lib/flow/sol-flow-node-options.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/flow/sol-flow-node-options.c b/src/lib/flow/sol-flow-node-options.c
index 0cbd0839e..8d5b9904b 100644
--- a/src/lib/flow/sol-flow-node-options.c
+++ b/src/lib/flow/sol-flow-node-options.c
@@ -465,7 +465,7 @@ direction_vector_parse(const char *value, struct sol_flow_node_named_options_mem
     return 0;
 
 err:
-    SOL_ERR("Invalid direction_vector value for option name=\"%s\": \"%s\"."
+    SOL_DBG("Invalid direction_vector value for option name=\"%s\": \"%s\"."
         " Please use the formats"
         " \"<x_value>|<y_value>|<z_value>|<min_value>|<max_value>\","
         " in that order, or \"<key>:<value>|<...>\", for keys in "