From ff9f6644cb79d3ea5271c783704eb5092f503612 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 28 Mar 2011 12:59:18 -0700 Subject: [PATCH] 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. --- ovsdb/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ovsdb/file.c b/ovsdb/file.c index 9f0ab280..1425bebe 100644 --- 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); -- 2.30.2