ovsdb: Raise database corruption log level from warning to error.

If there's database corruption then it indicates that something went wrong,
e.g. the machine was powered-off by power failure.  It's definitely
something that the admin should know about.  This sounds like an error to
me, so use that log level.

diff --git a/ovsdb/file.c b/ovsdb/file.c
index 9f0ab28043ac11148539ee9d33475e793c41a2d4..1425bebec549fbc3b022d2c4d54f703673179db9 100644 (file)
--- a/ovsdb/file.c
+++ b/ovsdb/file.c
@@ -230,7 +230,7 @@ ovsdb_file_open__(const char *file_name,
          * truncated due to power failure etc. and we should use its current
          * contents. */
         char *msg = ovsdb_error_to_string(error);
-        VLOG_WARN("%s", msg);
+        VLOG_ERR("%s", msg);
         free(msg);
 
         ovsdb_error_destroy(error);